The Model Context Protocol (MCP) is the plumbing that lets an AI agent — Claude, ChatGPT, Cursor — read and act on an external system through a standard interface instead of a bespoke integration. Anthropic introduced it as an open standard in November 2024. Eighteen months later, WordPress has adopted it at the platform level, and Automattic is saying the quiet part out loud: it wants WordPress to be “the operating system of the agentic web.”
This is the most strategically interesting thing happening in the WordPress ecosystem right now, and most WordPress publishers aren’t covering it rigorously. Here’s the landscape.
What changed in 2026
The timeline moved fast:
- Oct 2025 — WordPress.com adds MCP support, read-only. Agents could see your site; they couldn’t touch it.
- Mar 2026 — WordPress.com ships full write support. An agent can create posts, build pages, manage comments, organize tags and categories, and handle media through natural conversation. The surface today is twelve tools, and it reaches past content into domains, DNS, and billing.
- Mar 2026 — WordPress.org ships an official Plugin Directory MCP server, so plugin authors can validate a
readme.txt, check review status, and submit a plugin without leaving their editor. - 2026 — the self-hosted path matures. The core Abilities API defines what a site can do; the official MCP Adapter (part of the WordPress AI Building Blocks initiative) exposes those abilities as MCP tools and scopes every action through per-transport permission callbacks.
That last piece matters most. The early Automattic/wordpress-mcp repository was archived in January 2026 and development consolidated into the official WordPress/mcp-adapter (currently v0.5.0), maintained by the core AI team. MCP for WordPress is no longer a side experiment — it’s an official building block with a release cadence.
How it actually works
Three layers, worth keeping straight because the marketing blurs them:
- Abilities API — a core registry of what a WordPress install can do (publish a post, upload media, run a WP-CLI-style action). This is the capability layer.
- MCP Adapter — translates those abilities into MCP tools an agent can call, and translates the agent’s calls back into REST API actions. This is the protocol bridge.
- Auth — every agent connection is authenticated and scoped to a user’s capabilities. An editor-scoped connection can’t do admin things. This is the safety layer, and it’s the difference between “useful” and “reckless.”
Most write-ups get that third layer wrong, so it’s worth being precise: the two official paths do not share an auth model. WordPress.com’s hosted server uses OAuth 2.1 with PKCE and token rotation, and stores no client secret on your machine. The self-hosted MCP Adapter authenticates its HTTP transport with WordPress Application Passwords — the same mechanism the REST API has used since 5.6 — with WP-CLI user auth on the STDIO transport, and a replaceable permission callback if you need something stricter. Both are defensible choices; they are not the same choice, and an application password is a long-lived credential in a way an OAuth token is not.
A “capability” exposed over MCP means the server offers that tool. Whether the agent can actually use it still depends on the permissions of the authenticated user — a distinction our MCP registry calls out on every entry, because conflating the two is how people talk themselves into unsafe setups.
The plugin route is here today
You don’t have to wait for everything to standardize. The most mature MCP-for-WordPress implementation in publication right now ships inside an existing, well-distributed plugin: AI Engine by Meow Apps. Its Pro tier exposes an authenticated MCP server endpoint covering post management, media, user metadata, WooCommerce (with the add-on), and WP-CLI bridges — surfaced in our MCP server registry.
The reason it’s the most mature isn’t superior engineering so much as distribution: it’s bolted onto a plugin already installed on 100,000+ sites. The official core adapter is the future; an established plugin is the present. WooCommerce has also shipped its own MCP integration, which tells you where the commerce side is headed.
Why this is a genuine strategic bet
Automattic’s “operating system of the agentic web” framing isn’t just a slogan. The logic: if agents become how people interact with software, the platforms that expose clean, standard, permissioned capabilities become the ones agents build on. WordPress already powers a huge share of the web and is open-source. Giving it a first-class agent interface is a credible play to make it the default substrate agents target.
Whether it works depends on execution — auth that’s safe by default, abilities that are genuinely useful, and a developer experience that doesn’t require a PhD. But the direction is deliberate and well-resourced, and that’s rare enough in standards adoption to take seriously.
What it means for you
- Site owners on WordPress.com paid plans: you can connect an agent today and have it draft and manage content conversationally. Start read-only, scope permissions tightly, and treat write access the way you’d treat handing someone your admin login.
- Self-hosted site owners: the official adapter is maturing; AI Engine’s MCP endpoint is the pragmatic option now. Either way, OAuth scoping is the feature to understand before the feature list.
- Developers: learn the Abilities API. Registering a clean ability is becoming the way to make your plugin’s functionality available to every agent at once — the new “does it have a good REST API,” raised a level.
Update: the protocol underneath this is about to change
Since this report was published, MCP has locked its 2026-07-28 revision — the largest since the protocol launched. It removes the initialize handshake and protocol-level sessions entirely, deprecates Roots, Sampling and Logging, and tightens authorization. The official WordPress MCP Adapter currently targets 2025-11-25, the revision it supersedes.
None of the landscape below stops being true, but the plumbing under it moves. We’ve written that up separately: what the 2026-07-28 MCP spec changes for WordPress.
The call
MCP for WordPress crossed from experiment to official building block in 2026. If you publish on WordPress, this is the platform shift worth tracking — not because you need to wire up an agent this quarter, but because the capability surface your site exposes to agents is about to matter the way mobile-responsiveness started mattering in 2012. Start with read-only, respect the permission model, and watch the official adapter. We’re tracking the server landscape entry by entry in the MCP registry.
Methodology
Dates and version numbers reflect Automattic, WordPress.com, and WordPress core AI-team sources current to mid-2026. The “most mature implementation” assessment is editorial, based on capability breadth and distribution among the servers tracked in our registry; it will shift as the official adapter and competing plugins evolve. Next AI-pillar report: an MCP server capability comparison once the field has more than a handful of production entries.