Skip to content
Agent Abilities for MCPAgent Abilities

Abilities from other plugins

WordPress 6.9 added the Abilities API, which lets any active plugin register its own abilities. Starting in version 1.1.0, Agent Abilities for MCP can bridge those, exposing them as governed MCP tools alongside its own built-in catalog. So your agent reaches the things other plugins already know how to do, without those plugins each shipping their own MCP server.

Separate from the built-in 153

Section titled “Separate from the built-in 153”

The built-in catalog is 153 governed abilities: 83 across WordPress core and 70 from auto-detected integrations. Bridging is a separate, dynamic layer on top of that. The available set depends on which of your other plugins register abilities, so it is site-specific. Two sites running different plugins will see different bridged abilities.

How to enable it

Section titled “How to enable it”

Open the “Other plugins” admin screen. Bridged abilities are grouped by the plugin that registered them, so you can see at a glance what each one brings in.

Every bridged ability is off by default. The admin turns each one on, exactly like the core abilities. You can enable or disable a whole plugin’s set at once when you want to, but nothing is exposed until you choose it.

Governed like the rest

Section titled “Governed like the rest”

Once you enable a bridged ability, it runs under the same governance model as the built-in catalog:

  • Scoped to the bound WordPress user, so it can only do what that user can do.
  • Capability re-checked on every call, not just at connect time.
  • Rate-limited under the same controls.
  • Written to the same audit log, with argument values never stored.

What you can bridge

Section titled “What you can bridge”

What can be bridged is whatever your active plugins expose, so the following are illustrations, not integrations this plugin builds or maintains. For example, Events Manager registers event, booking, and location abilities. WooCommerce registers its own native abilities, which are separate from this plugin’s built-in WooCommerce integration. As more plugins adopt the Abilities API, more becomes available to bridge, with no change needed here.

Not the mcp-remote client bridge

Section titled “Not the mcp-remote client bridge”

Do not confuse this with the mcp-remote client bridge, a local program some MCP clients use to connect to a server. Here “bridge” means bringing other plugins’ abilities into your governed set, not connecting a client.

Next steps

Section titled “Next steps”