WordPress Abilities API · guide
The WordPress Abilities API, and how MCP uses it.
The WordPress Abilities API is the part of WordPress core that lets code describe what a site can do in a form that software can discover and run. It arrived in WordPress 6.9, and it is the foundation that MCP tools for WordPress are registered on. This guide explains the API, how an ability becomes an MCP tool, and what WP MCP does on top of it.
Checked against the WordPress developer handbook on 11 November 2026
The API
What the WordPress Abilities API is.
In the words of the WordPress developer handbook, the Abilities API "provides a standardized way to register and discover distinct units of functionality within a WordPress site". Those units are called abilities. The API is available in WordPress 6.9 and above; theWordPress 6.9 dev note introduces it.
An ability is registered with a name in the form namespace/ability-name and a set of arguments:
labelanddescription: what the ability is, for people and for software.category: a registered category the ability belongs to.input_schemaandoutput_schema: JSON Schema for what it accepts and returns.execute_callback: the function that does the work.permission_callback: the check that decides whether the current user may run it.meta: extra data, includingshow_in_rest, which exposes the ability over the REST API.
Abilities are registered on the wp_abilities_api_init action withwp_register_ability(). Categories are registered separately, onwp_abilities_api_categories_init, with wp_register_ability_category(). A minimal example:
a minimal ability (see the handbook for the full reference)
add_action( 'wp_abilities_api_categories_init', function () {
wp_register_ability_category( 'my-plugin', array(
'label' => 'My Plugin',
'description' => 'Abilities provided by My Plugin.',
) );
} );
add_action( 'wp_abilities_api_init', function () {
wp_register_ability( 'my-plugin/count-drafts', array(
'label' => 'Count drafts',
'description' => 'Returns the number of draft posts.',
'category' => 'my-plugin',
'output_schema' => array( 'type' => 'integer' ),
'execute_callback' => function () {
return (int) wp_count_posts()->draft;
},
'permission_callback' => function () {
return current_user_can( 'edit_posts' );
},
'meta' => array( 'show_in_rest' => true ),
) );
} );Once registered, an ability can be looked up with wp_get_ability(), listed withwp_get_abilities(), and run with its execute() method, which validates the input and runs the permission check first. Abilities are not exposed over REST unless their author sets meta.show_in_rest to true; those that are appear under thewp-abilities/v1 REST namespace.
Abilities and MCP
How an ability becomes an MCP tool.
Plugin
Registers an ability
Name, schemas, permission check, callback.
Core
Abilities API
One registry of what the site can do.
MCP Adapter
Translates
Abilities become MCP tools on an endpoint.
AI client
Calls the tool
Claude, Cursor or another MCP client.
The Abilities API does not speak MCP by itself. The Model Context Protocol is the open standard AI clients use to call tools on a server, and the bridge between the two is theWordPress MCP Adapter, the WordPress project's package for MCP, which translates registered abilities into MCP tools and resources. It is a separate package (WordPress/mcp-adapter), not part of the Abilities API itself.
The practical result: a plugin author describes a capability once, with a schema and a permission check, and any MCP client can then discover and call it as the signed-in WordPress user. What core does not ship is a set of site-management tools, or an undo for what those tools change.
WP MCP on the Abilities API
How WP MCP registers its abilities.
WP MCP is a plugin built on this API. It registers a wpmcp category and then407 abilities (274 in the free plugin, 133 on Pro) onwp_abilities_api_init, each named wpmcp/ followed by the tool name, for example wpmcp/update-post. Tools for a plugin such as WooCommerce or Elementor are registered when that plugin is active.
It serves them over MCP at /wp-json/mcp/wpmcp-server through the official MCP Adapter. WP MCP bundles a copy of the adapter so it works alone, and uses the standalone MCP Adapter plugin instead when that is active. The WordPress MCP adapter guideshows the adapter end to end: register an ability, expose it as a tool and call it.
What WP MCP adds on top of the API:
- Every ability checks a WordPress capability, so an agent can never do more than the user it signs in as.
- Every ability that writes goes through one engine that saves a snapshot first, which is what makes one-click undo possible.
- Risky abilities (database writes, file writes, package updates, WP-CLI, PHP execution) ship off until the site opts in.
- Governance rules and an audit log sit in front of every call.
See the WordPress MCP server page for the architecture and thetools reference for the full list.
The ability bridge
Running other plugins' abilities, off by default.
As more plugins register abilities of their own, an agent connected to WP MCP can reach them through the ability bridge: three tools, list-site-abilities, get-site-ability andexecute-site-ability. The bridge ships off. Exposing every ability another plugin registered would be a surprise, so nothing is bridged until a site administrator opts in:
switch the ability bridge on
// wp-config.php, above "That's all, stop editing!"
define('WPMCP_ENABLE_ABILITY_BRIDGE', true);
// or, from a plugin or mu-plugin
add_filter('wpmcp_enable_ability_bridge', '__return_true');Opening the bridge does not widen access. What it does, and does not do:
- Only abilities their author exposed with
meta.show_in_restare reachable. Anything else answers as if it did not exist. - The target ability's own permission check always runs. There is no setting that skips it.
- Each bridged ability is also checked against WP MCP's governance rules, and every call, refusals included, is written to the audit log.
- A site can narrow the bridge to named abilities or namespaces with the
WPMCP_ABILITY_BRIDGE_ALLOWLISTconstant or thewpmcp_ability_bridge_allowlistfilter. - Bridged calls are not covered by undo. WP MCP cannot know how another plugin's code changes the site, so results are marked as not reversible.
Frequently asked
WordPress Abilities API: questions, answered.
What is the WordPress Abilities API?
It is a core WordPress API that gives plugins, themes and core one standard way to register and discover units of functionality, called abilities. Each ability has a name, a description, input and output schemas, a permission check and a callback, so both people and software can find out what a site can do and run it safely.
Which WordPress version includes the Abilities API?
WordPress 6.9. The API is available in WordPress 6.9 and above, which is why WP MCP requires 6.9 or newer.
Is the Abilities API the same as MCP?
No. The Abilities API is how functionality is registered inside WordPress. MCP, the Model Context Protocol, is how an AI client talks to a server. The WordPress MCP Adapter connects the two by translating registered abilities into MCP tools that a client like Claude or Cursor can call.
What are WordPress MCP abilities?
They are abilities registered through the Abilities API and exposed to AI clients as MCP tools. WP MCP registers 407 of them (274 free, 133 on Pro), each named wpmcp/ followed by the tool name, such as wpmcp/update-post.
Do I need to write code to use the Abilities API?
Only if you are a developer adding abilities of your own. To let an AI agent work on a site you install a plugin that registers abilities and serves them over MCP. WP MCP does both, with a snapshot before every write.
Can WP MCP run abilities registered by other plugins?
Yes, through its ability bridge, which is off by default. Once a site opts in, an agent can list and run abilities that other plugins registered and marked as exposed. The other plugin's own permission check always runs, and bridged calls are not covered by undo.
Sources: the Abilities API handbook and theWordPress 6.9 dev note for core, theMCP Adapter announcement for the adapter. The API is young and may change; the handbook is the authority.
Read next
WordPress MCP adapter guide →
Register an ability, expose it as an MCP tool, call it through the adapter and see how WP MCP uses it.
What is an MCP server? →
Hosts, clients, tools and transports in plain language, with a WordPress site as the worked example.
MCP vs API →
What really differs, when a plain REST API is the better choice, and the same WordPress job done both ways.
MCP OAuth explained →
How authorization works for remote MCP servers, and when an application password is enough.
How to build an MCP server →
The JSON-RPC handshake with curl, then the WordPress route through the Abilities API.
MCP server examples →
Real MCP servers by category, what each exposes, and a WordPress site as the worked example.