Agents Operate Naively
Claude, Codex, Cursor - any agent that speaks MCP can connect to WordPress. Agents operate WP naively, through code, direct DB reads and writes, etc.
PLUGIN-SPECIFIC ABILITIES
Ability Packs
Install in one click from the Abilities screen inside Agent Connector, and its abilities show up automatically — here's how.
Contact Form 7
WordPress.org ↗
Available
Forms, fields, mail templates, validation messages, and settings — everything in the CF7 editor.
GitHub
Yoast SEO
WordPress.org ↗
Available
Per-post and per-term SEO, titles and metas, site-wide settings, and content discovery.
GitHub
Maintenance
WordPress.org ↗
Available
Toggle maintenance mode, edit the page's content and design, set images from a URL.
GitHubmore packs on the way
A temporary solution, designed to be deprecated.
Your agent can already connect to WordPress. But most plugins haven't registered Abilities yet. As MCP and agentic control of WordPress takes off in the coming months, that will change. When a plugin registers its own abilities, our unofficial pack covering it gets deprecated.
Ability Packs
Ability Packs are add-on plugins for Agent Connector that register abilities for plugins that don't have official ones yet. Deliberately temporary, and designed to be deprecated.
Plugins Register Their Own Abilities
The official WordPress Abilities API is great, and we predict it will become widely used. Then, our Ability Packs become unnecessary.
Frequently asked questions
What is an ability pack?
An ordinary WordPress plugin. Each one registers abilities for a specific plugin through the WordPress Abilities API. Agent Connector exposes those abilities to your agent automatically.
Why do ability packs exist?
Without abilities, an agent falls back to doing everything the naive way — Universal Abilities can read and write any post, option, or database row, but the agent has to reverse-engineer each plugin's internals call by call. A pack gives it plugin-specific MCP tools that already know the plugin's data structures and rules.
Why are they "unofficial"?
We didn't build the plugins these packs cover, and we think abilities belong in the covered plugin directly. The packs are our attempt at coverage in the meantime.
How long will they exist?
Until they're not needed. When a plugin's developer registers official abilities, we deprecate our pack in its favor. We hope every pack on this page eventually disappears.
Plugin developers
Make our pack unnecessary
The best version of an ability pack is the one we never have to build. Register abilities directly in your plugin with the WordPress Abilities API — every Agent Connector site exposes them to agents automatically, with permissions handled for you.
If we cover your plugin with an unofficial pack, we'll deprecate it the moment you ship official abilities. Our packs are GPL — fork one as a starting point.
add_action( 'wp_abilities_api_init', function () {
wp_register_ability( 'my-plugin/do-thing', array(
'label' => 'Do Thing',
'description' => 'Does the thing.',
'category' => 'my-plugin',
'execute_callback' => fn( $in ) => array( 'done' => true ),
'meta' => array( 'mcp' => array( 'public' => true ) ),
) );
} );