On October 7, 2026, WordPress pushed the canonical MCP Adapter plugin to the official directory. It had already racked up over 40,000 installations from GitHub releases before it ever touched wordpress.org. That number alone tells you something: developers were not waiting for an official blessing. They were wiring AI into their sites anyway, and WordPress decided it was time to hand them a proper cable.

If you run a WordPress site and you have been ignoring the AI integration wave because it felt like hype, this is the moment to pay attention. Not because AI is going to replace your website, but because the protocol that connects AI to your site just became a first-class citizen in the WordPress ecosystem.

What MCP actually is

MCP stands for Model Context Protocol. Anthropic developed it as an open standard that lets AI systems — chatbots, agents, coding assistants, whatever comes next — securely connect to applications, data sources, and tools. Think of it as a universal adapter plug. Before MCP, every AI integration was a bespoke hack. An AI agent that wanted to read your WordPress posts needed custom code to talk to the REST API. One that wanted to publish a post needed a different custom integration. Every plugin, every theme, every custom post type was its own silo.

MCP changes that by giving AI a standardized way to discover what a site can do and then do it. The adapter exposes WordPress's capabilities — reading content, creating posts, managing options, calling plugin functions — through a single protocol that any MCP-compatible AI client can understand. Claude, ChatGPT, Gemini, Cursor, VS Code with an MCP extension, or your own custom agent running on n8n. They all speak the same language now.

Jason Adams, Director of Engineering for AI at Automattic, announced the release on X: "This is the canonical MCP plugin for WordPress, carefully architected for backwards-compatibility with MCP versions. If you want MCP in your site or plugins, I highly recommend using this."

Why backwards compatibility matters here

Adams specifically called out backwards compatibility, and that is not a throwaway line. The MCP protocol itself is still evolving. Anthropic ships updates, adds new capabilities, and sometimes changes how things work. If WordPress had built an adapter that only supported today's MCP version, every protocol update would have broken thousands of sites.

The canonical adapter uses WordPress's Abilities API to abstract the connection layer. When MCP changes, the adapter can update its protocol handling without touching the WordPress-side code. Plugins that register abilities through the standard API will keep working regardless of which MCP version the client is using. This is the kind of boring infrastructure decision that saves everyone a massive headache in six months.

It also means plugin developers can build MCP-compatible features without worrying about which specific MCP version their users are running. A WooCommerce extension that exposes product data through the Abilities API will work with any MCP client, now and in the future. That is a big deal for the ecosystem.

What you can actually do with it

Once the MCP Adapter is installed, an AI agent with MCP support can interact with your site in ways that used to require custom API development. The practical list includes reading and searching your content, creating and editing posts and pages, managing media uploads, querying plugin data, and executing WordPress functions through registered abilities.

Here is where it gets interesting for anyone running a business on WordPress. Imagine an AI assistant that can audit your site's SEO, identify posts with missing meta descriptions, and fix them — all through a standardized protocol, without scraping your site or hitting rate limits on the REST API. Or a content agent that drafts a post, uploads the featured image, assigns categories, and schedules publication, all as a single automated workflow.

The plugin ecosystem is where this will really take off. A contact form plugin that exposes form submissions through MCP means an AI agent can read and respond to inquiries without you building a custom integration. An e-commerce plugin that exposes order data means an AI can handle customer service queries with real context about what the customer ordered and when.

The security question you should be asking

Every time AI gets deeper access to a system, the security conversation gets more important. The MCP Adapter handles authorization through WordPress's existing permission system, which means an AI agent connected through MCP has the same capabilities as the user credentials it is authenticated with. If you connect an AI agent with an admin-level application password, it can do everything an admin can do. If you connect it with an editor-level account, it can create and edit content but not change settings or install plugins.

This is the right design choice, but it puts the responsibility on you. The same advice from every security guide applies here with extra urgency: use the principle of least privilege. Create a dedicated application password for your AI agent with only the permissions it actually needs. Do not connect an AI agent with your admin account because it is convenient.

Also worth noting: the adapter runs on your server. Your data does not go through a third-party service to reach the AI. The AI connects to your site directly through the protocol. That is better for privacy than most AI integrations, but it means your site's security posture matters even more, because the attack surface just expanded.

What this means for the WordPress ecosystem

WordPress powers roughly 40% of the web. MCP becoming a first-class integration layer means AI agents will increasingly treat WordPress sites as native tool endpoints rather than websites to scrape. That is a fundamental shift in how the platform interacts with the AI ecosystem.

For site owners, the immediate action item is simple: install the adapter if you want AI tools to interact with your site through a standard protocol. Skip it if you are not ready for AI integration — the plugin does nothing until an MCP client connects to it.

For developers, the message is more pointed: start registering your plugin's capabilities through the Abilities API. The plugins that expose their functionality through MCP will be the ones that AI agents can actually use. The ones that do not will be invisible to every MCP-connected tool on the market.

The WordPress MCP Adapter is version 0.70, which tells you it is early and things will change. But 40,000 sites were already running it before it hit the official directory. The protocol is real, the ecosystem is building on it, and WordPress just made sure it has a seat at the table.

Sources: Search Engine Journal — WordPress Releases Canonical MCP Adapter Plugin (October 7, 2026). WordPress.org — MCP Adapter Plugin.