WordPress 6.9 shipped the Abilities API, and core's AI team followed it with an official wordpress/mcp-adapter package that bridges those Abilities to the Model Context Protocol. If you've searched for "wordpress mcp adapter" or "mcp for wordpress" recently, you've probably landed on both that announcement and on hosted tools like WP MCP — and it's not obvious how they relate. Here's the actual difference.
What the official MCP Adapter does
The Abilities API is a core primitive: plugins register typed "Abilities" — discrete capabilities like "get site info" or "create a post" — that AI agents can discover and call. The MCP Adapter package then exposes whatever Abilities exist on a site over the MCP protocol, so a client like Claude Desktop can connect directly.
Out of the box, WordPress core only registers three abilities: site info, user info, and environment info. Anything beyond that — posts, WooCommerce, Elementor, forms, SEO — has to be built by a plugin author registering its own Abilities, or coded by you. It's a foundation, not a finished tool, and it requires a developer to extend it for real work.
What WP MCP does
WP MCP is a hosted MCP server that already speaks to your site's standard REST API and ships with 1,836 tools covering content, WooCommerce, Elementor, SEO, forms, code, analytics, backups, users, themes, and plugins. There's no plugin to install and nothing to register — you connect with an Application Password, paste a server URL into Claude, and every tool is available immediately.
Side-by-side
| WordPress core MCP Adapter | WP MCP | |
|---|---|---|
| Setup | Requires a developer to register custom Abilities per feature | Connect with an Application Password — no plugin install |
| Tools out of the box | 3 (site/user/environment info) | 1,836 across the whole admin |
| WooCommerce / Elementor / SEO | Only if a plugin author builds Abilities for them | Built in |
| Hosting | Self-hosted, runs inside your WordPress install | Managed cloud endpoint |
| Best for | Plugin developers building custom AI-callable Abilities | Site owners and agencies who want Claude managing the site today |
Which one should you use?
If you're a plugin developer who wants to expose a specific custom capability to AI agents as part of your plugin, the Abilities API and core MCP Adapter are the right primitive to build on. If you're a site owner, store manager, or agency who wants Claude to actually run your WordPress site — write posts, manage WooCommerce orders, edit Elementor pages, audit SEO — without writing any code, WP MCP gets you there in minutes instead of requiring you to build the Abilities layer yourself.
The two aren't really competitors so much as different layers: core's Abilities API standardizes how a site exposes capabilities; WP MCP is a ready-to-use set of 1,836 capabilities already built.
Skip building your own Abilities layer.
Connect Claude to your WordPress site with 1,836 tools already built in.
Get Started Free →