MCP is how AI agents such as Claude, ChatGPT and Cursor call tools on a WordPress site. This is the practical map for 2026: what the official MCP Adapter does, how it compares with WordPress.com's server, the plugin options and WPOS, and what to check before an agent touches a client site.
The Model Context Protocol is an open standard for connecting AI agents to tools. An MCP server publishes a list of operations with typed inputs; an MCP client such as Claude, ChatGPT, Cursor, VS Code or Codex discovers them and calls them on the model's behalf. On WordPress, that means an agent can look up posts, change settings or create a page through tools the site has chosen to publish, instead of guessing its way around wp-admin.
MCP is not a permission system on its own. The server decides which tools exist; WordPress roles and the server's own checks decide who can run them. Two sites with the same MCP plugin can expose very different power depending on the user the agent connects as. Most of what goes wrong with agents on WordPress is a permissions decision someone skipped, not a protocol problem.
The official route has two parts. The Abilities API, added in WordPress 6.9, lets core, plugins and themes register abilities: named actions with an input schema, an output schema, a permission check and the code that runs. The MCP Adapter, the WordPress project’s official plugin, publishes those abilities to MCP clients as tools, resources and prompts.
meta.public, or meta.mcp.public for MCP only, to true.mcp-adapter-default-server, gives a client three tools: mcp-adapter/discover-abilities, mcp-adapter/get-ability-info and mcp-adapter/execute-ability./wp-json/mcp/mcp-adapter-default-server, usually reached through Automattic’s @automattic/mcp-wordpress-remote proxy and an application password.Out of the box it exposes little: core ships a few read-only abilities such as site, user and environment information. The adapter becomes useful as the plugins you run register abilities of their own, which is why most people who want broad tools today install an MCP plugin instead. Automattic’s earlier wordpress-mcp plugin is archived, and the MCP Adapter is now the recommended package.
For a worked example of registering an ability and calling it from Claude, see the Abilities API and MCP Adapter guide.
Most sites will choose between a handful of options. Installs are WordPress.org active installs on 30 October 2026. WPOS is our product and isn’t distributed through WordPress.org.
| Option | From | Installs | What it is |
|---|---|---|---|
| WordPress.com MCP | Automattic | via Jetpack | Hosted server with OAuth 2.1 and read and write tools; self-hosted sites connect through Jetpack |
| WPVibe | SeedProd | 100,000+ | MCP server for content, themes and settings, with approvals |
| AI Engine | Meow Apps | 90,000+ | AI chatbot and toolkit with a built-in MCP server |
| MCP Adapter | WordPress project | 60,000+ | Official bridge from the Abilities API to MCP |
| Easy MCP AI | Themeisle | 30,000+ | Free MCP server with 280+ tools, including WooCommerce, SEO and GA4 |
| Royal MCP | Royal Plugins | 10,000+ | 250+ tools with OAuth 2.0, fully self-hosted |
| Secure MCP Server | miniOrange | 8,000+ | 400+ tools, built around security controls |
| Elementor Ultra | WPOS team, open source | npm | About 90 Elementor 4 tools and a JSX compiler for native pages |
| WPOS | WPOS | — | Exposes the tools of WPOS’s built-in agent over MCP: native Gutenberg, Elementor and Divi builds, media, users, SEO, WooCommerce and read-only inspection, with per-page backups |
Profiles, trade-offs and how to choose are in the full comparison of WordPress MCP plugins.
The protocol is the easy part. These six decisions are where agent mistakes are made or prevented.
Give the agent its own WordPress account with only the capabilities the job needs. An Editor can change content; it cannot install plugins.
Use read-only access for the first tasks. You learn what the agent reaches for before it can change anything.
OAuth or an application password, never a person's own login, so access ends the moment a tool or contractor does.
Point the agent at a staging copy for anything it has not done before, then promote what you have checked.
A backup you have never restored is a hope. Know how long a rollback takes before you need one.
Let the agent draft and prepare. Let a person approve what customers will see.
What MCP does on a WordPress site, which server to use, and where WPOS fits.
It is the use of the Model Context Protocol to let AI agents call tools on a WordPress site. A WordPress MCP server, such as the official MCP Adapter, WordPress.com's server, a plugin or WPOS, publishes tools; an MCP client such as Claude, ChatGPT or Cursor calls them.
The WordPress project's official plugin for MCP. It turns abilities registered through the Abilities API into MCP tools, resources and prompts, needs WordPress 6.9 or later, runs over STDIO with WP-CLI or over HTTP, and only exposes abilities a developer has marked public.
No. Plugins such as WPVibe, AI Engine, Easy MCP AI and Royal MCP run their own MCP servers. The adapter matters when you want the standard, open route, or when plugins you rely on register abilities you want agents to use.
Yes, for self-hosted sites connected through the Jetpack plugin. WordPress.com's documentation says those sites use the same MCP server and tool catalogue as sites hosted on WordPress.com.
Any client that implements MCP. WordPress.com documents Claude Desktop, Claude Code, ChatGPT, Codex and Cursor, and the MCP Adapter's guide covers Claude Desktop, Claude Code, Cursor and VS Code.
Yes. WPOS speaks MCP, so Claude Code, Cursor, Codex or any MCP client can drive the same tools as WPOS's built-in agent across the sites in your workspace, and your own agent doesn't spend WPOS credits. WPOS is also an agent and workspace in its own right, inside wp-admin. For Elementor 4 builds from Claude Code, the team also maintains the open-source Elementor Ultra.
Nothing for 30 days: 5,000 credits, a live site plus a staging sandbox, and no card. After that it is $25 per site, dropping to $19.50 as you add sites. Credits pay for work done by WPOS's own agent.
Go deeper on WordPress MCP:
WPOS runs the work across your client sites, from its own agent or yours. Free for 30 days: 5,000 credits, a live site plus a sandbox, no card.
Start free