Two names come up together in WordPress AI discussions: the Abilities API and MCP. They are related but not the same thing, and mixing them up leads to confusing designs. This guide explains what each one is, how they connect, and when you need which.
The Abilities API is part of WordPress core in recent versions, and MCP is an open protocol from outside WordPress. Both are evolving, so verify details against the current official documentation before you build.
What Is the WordPress Abilities API?
The Abilities API is a WordPress feature, available in core since version 6.9, that keeps a central registry of things a site can do. Plugins, themes, and core can register an “ability” with a name, a description, an input schema, and callbacks. Other systems can then discover and run those abilities.
You register an ability in PHP with wp_register_ability(), inside a callback hooked to the wp_abilities_api_init action.
What Is MCP?
MCP, the Model Context Protocol, is an open protocol that lets AI applications discover and call tools exposed by a server. It is not specific to WordPress.
How They Relate
The Abilities API describes what a WordPress site can do. MCP is how an AI client asks for and runs tools. The MCP Adapter bridges the two: it takes abilities from the registry and exposes them as MCP tools, resources, and prompts.
| Abilities API | MCP | |
|---|---|---|
| What it is | A WordPress-side registry of capabilities | A protocol for AI clients to use tools |
| Lives in | WordPress core (6.9 and later) | Outside WordPress, used by many systems |
| Main users | Plugin and theme developers, other WordPress code | AI clients and MCP servers |
| Defines | Names, schemas, permissions, callbacks | How tools are listed and called |
| Connects to AI via | A bridge such as the MCP Adapter | Directly, as the protocol itself |
The MCP Adapter
The MCP Adapter is an official WordPress project that bridges the Abilities API to MCP. According to its documentation:
- Registered abilities can become MCP tools, resources, and prompts.
- It creates a default MCP server, reachable over HTTP and STDIO.
- Abilities marked public through their
meta.publicsetting are discoverable on the default server. - You can also build custom servers that list specific abilities.
- It supports per-ability permission checks.
Exact behavior depends on your WordPress and adapter versions, so read the current adapter documentation.
A Small Ability Example
This example follows the shape used in the adapter’s documentation. It is an illustration, not a complete plugin. Check the current docs for required fields, such as how categories are registered.
add_action( 'wp_abilities_api_init', function () {
wp_register_ability( 'my-plugin/get-site-info', [
'label' => 'Get Site Information',
'description' => 'Retrieves basic information about the site',
'category' => 'site',
'input_schema' => [
'type' => 'object',
'properties' => [],
],
'execute_callback' => function ( $input ) {
return [
'name' => get_bloginfo( 'name' ),
'url' => home_url(),
];
},
'permission_callback' => function () {
return current_user_can( 'read' );
},
'meta' => [ 'public' => true ],
] );
} );
Once registered and marked public, the MCP Adapter can expose this ability to an AI client, subject to its permission check.
When to Use Which
| You want to | Use |
|---|---|
| Define a reusable capability inside a plugin or theme | The Abilities API |
| Let AI clients call that capability | The Abilities API plus an MCP bridge such as the MCP Adapter |
| Build an MCP server unrelated to WordPress | MCP directly |
| Expose WordPress features to AI without writing PHP | An existing WordPress MCP plugin |
Why the Abilities API Helps
- One definition, many uses. The same ability can be used by other WordPress code and by AI clients.
- Standard structure. Schemas and permission callbacks are built in.
- Less custom plumbing. You do not write a new MCP tool for every feature.
Security Considerations
- Write a real
permission_callbackfor every ability. Do not return true for sensitive actions. - Only mark abilities public if you want them discoverable.
- Prefer read-only abilities first.
- Test with a limited user, and require authentication on the MCP endpoint.
Troubleshooting
My Ability Does Not Appear in MCP
Check that it is registered on wp_abilities_api_init, marked public or explicitly listed, and that the MCP Adapter is active.
I Get Permission Errors
The connected user must satisfy your permission callback.
It Works on One Site but Not Another
Check WordPress and adapter versions. The Abilities API needs a WordPress version that includes it.
Frequently Asked Questions
Is the Abilities API the same as MCP?
No. The Abilities API is a WordPress registry of capabilities. MCP is a protocol AI clients use to call tools.
Do I need both?
To expose registered abilities to AI clients, you use the Abilities API with an MCP bridge. For other cases, one may be enough.
What is the MCP Adapter?
An official WordPress project that exposes abilities as MCP tools, resources, and prompts.
Which WordPress version has the Abilities API?
It is part of core from WordPress 6.9. Check current documentation for newer changes.
Conclusion
The Abilities API and MCP work at different layers. The Abilities API defines what your WordPress site can do, and MCP lets AI clients use it. The MCP Adapter connects them. Start with read-only abilities and strict permission callbacks.
Continue with how MCP Manager bridges WordPress and AI assistants and the WordPress 7.0 feature guide.
Explore ByteCore Stack Plugins
- MCP Manager β connect your WordPress site to AI assistants through MCP.
- SMTP Manager β reliable WordPress email delivery.
- Lightsail Manager β manage your AWS Lightsail CDN from WordPress.
