What is a bridged ability?
A bridged ability is one that another active plugin registers through the WordPress 6.9 Abilities API, which Agent Abilities then exposes as a governed MCP tool. It is not part of the built-in catalog. It comes from a plugin you already run, and it stays off until you switch it on.
How is bridging different from the built-in integrations?
The built-in integrations, such as WooCommerce and Advanced Custom Fields, are ones we build and maintain as part of the plugin, 94 abilities in all and counted in the fixed 184 catalog. Bridged abilities are registered by your other plugins, not by us, so the set is dynamic and specific to your site. We do not write or maintain them; we govern how an agent reaches them.
Are bridged abilities on by default?
No. Every bridged ability starts off, the same as the core catalog. You enable each one yourself, and you can turn a whole plugin's set on or off in one click. Nothing another plugin registers reaches an agent through this plugin until you choose it. A plugin that publishes tools straight to the default server of the MCP Adapter skips this screen and these controls.
How many abilities can I bridge?
There is no fixed number. It depends entirely on which of your active plugins register abilities of their own. That is why we never quote a count for bridged abilities: the built-in catalog is a fixed 184, but bridging is a dynamic, site-specific set.
Are bridged abilities governed like core ones?
Yes. Once you enable a bridged ability, it inherits the whole governance layer: it is scoped to the connected user, the capability is re-checked before every call, it counts against the same rate limit, and every call lands in the same audit log, denials included.
What happens when another plugin adds new AI tools?
They stay off. Since 1.11.0, when a plugin update or a newly activated plugin adds tools, a “New tools since your last review” card on the Other plugins tab lists them, and Settings can send a notification. Nothing new reaches an agent through this plugin until you switch it on, and marking a tool as reviewed does not switch it on. The check runs when an administrator loads wp-admin, so a WP-CLI update or an auto-update shows up at the next admin visit. On the first admin load after upgrading, everything already listed counts as reviewed.
What does Allow only read tools do?
It sets one plugin to its read tools, after you confirm. That plugin’s other tools turn off, saved selections for its tools that are not on now are removed, and its tools count as reviewed. A tool counts as a read only when the plugin labels it read-only, so a plugin with no such label ends up with nothing on. Other plugins are untouched.
Does it warn me when a tool may return personal data?
Yes, as a hint. The Other plugins tab puts a notice on a tool when its plugin or tool name suggests it may return personal data, such as form entries or orders. Learner and member tools are caught only by words in the tool name, so some will carry no notice. It is not a full check, so treat any tool from another plugin as able to return personal data. This plugin does not filter what another plugin’s ability returns.