Agent Abilities
GitHubGet it free
Features
Abilities
Browse all abilities

WordPress core

ContentTaxonomies & TermsCommentsUsersMediaSite settingsPluginsThemes & stylesBlocksMenusSearch

Integrations

WooCommerceAdvanced Custom FieldsRank Math SEOYoast SEOAll in One SEOSlim SEOThe Events CalendarEvent TicketsAvadaGeoDirectory
Integrations
All integrationsWooCommerce52Advanced Custom Fields7Rank Math SEO5Yoast SEO3All in One SEO3Slim SEO2The Events Calendar13Event Tickets3Avada2GeoDirectory4
Bridge
Bridge overviewPlugin directory196

Most installed

Elementor Website BuilderYoast SEOWooCommerceAkismet Anti-spamWPFormsRank Math SEOWP Mail SMTPWPCode
AI clients
All clientsChatGPTClaude.aiClaude DesktopManusClaude CodeCursorVS CodeWindsurfGemini CLI
Resources
DocsChangelogPrompt LibraryBlogComparisonsSupport
GitHubGet it free

Integrations / Avada

Governed integration

Avada MCP abilities

2 governed Avada abilities for AI agents. They appear on your WordPress MCP server only while the Avada theme with Fusion Builder is active, and stay off until you enable them. Read Fusion Builder markup, and replace text without touching the shortcode tree.

2 governed abilities Requires the Avada theme with Fusion BuilderGuarded write

Governed exactly like core

These abilities are off until you enable them, capability-checked before every call, and written to the same audit log as everything else. There is no separate trust model for integrations.

  • Active only while the Avada theme with Fusion Builder is installed and active
  • Off by default, enabled one ability at a time
  • Capability-gated on every call, discovery and execution separately
  • Logged like core, denials included, keys and identifiers, never free-text

How to turn it on

Activate the Avada theme with Fusion Builder, then open the Agent Abilities for MCP screen and enable the Avada abilities you want. Connect your client to the endpoint on the Connection tab. The address below is illustrative; your real one shows there.

Illustrative endpoint (your real one shows on the Connection tab)https://your-site.com/wp-json/…/mcp

The 2 Avada abilities

Each one is off until you enable it and capability-checked on every call. Open any card to see how it is governed.

Get Avada page content

Read only

Reads the raw post content of an Avada/Fusion Builder page, unchanged. Fusion Builder shortcodes are returned exactly as stored, never rendered or stripped. Response includes an is_avada_owned flag. Requires edit access to the post.

View ability

Replace text in an Avada page

Guarded write

Replaces literal text within an Avada/Fusion Builder page while requiring the Fusion shortcode tree to stay byte-identical before and after. A replacement that would touch a shortcode tag, its self-closing form, or an attribute is refused rather than risk breaking the layout. Requires edit access to the post.

View ability

Try it with a prompt

Example requests you could paste to your agent once Avada abilities are on.

  1. Read the Fusion Builder markup on page 41 so I can see how the layout is put together.
  2. Replace our old tagline with the new one on page 41, and stop if it would touch the layout.
  3. Check whether page 41 is actually built with Avada before we edit anything.

These are illustrative example prompts. The agent runs them as the user you connected, checked against that user's capabilities and written to your audit log.

Back to all integrations

Add Avada, keep the same control.

Every integration ability is off until you enable it, scoped to the user you connect, and logged like everything else. Turn on only what you need.

Get it on WordPress.orgRead the docs

Active only while its host plugin is on, and gated like core.