WordPress has published the canonical MCP Adapter plugin — version 0.70 — in the official WordPress.org plugin repository for the first time, giving site owners an official path to connect their sites, plugins, and PHP functions to AI systems. The plugin already counts over 40,000 installations from its earlier life as a GitHub-only release.

The release is confirmed by Automattic itself. Jason Adams, Director of Engineering, AI at Automattic, announced the launch on X, pointing users to the official listing at wordpress.org/plugins/mcp-adapter.

What is MCP and why does it matter for WordPress sites?

MCP (Model Context Protocol) is an open standard developed by Anthropic that allows AI systems to connect securely to apps, data, plugins, tools, and websites. Once connected, an AI system can access information and perform actions — not just read content.

For WordPress specifically, MCP enables AI to interact with:

• WordPress sites directly
• Installed plugins
• WordPress functions — PHP code snippets that perform specific tasks such as publishing posts

That last point is the significant one for publishers and SEO teams. A site exposing MCP endpoints is no longer a passive document source for AI agents; it becomes an environment where AI systems can take actions on the site itself, subject to authorization.

What did Automattic say about the release?

Adams framed the plugin as the canonical MCP implementation for WordPress and emphasized its engineering decisions around compatibility and authorization.

He wrote: "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."

He added: "It makes use of the Abilities API to avoid functional redundancy while handling authorization. I'm excited to see the pieces coming together!"

The word "canonical" carries weight here. Third-party MCP integrations for WordPress existed before this listing; with an official Automattic-backed plugin in the directory, WordPress now has a single reference implementation that plugin developers can build against rather than rolling their own protocol handling.

Why does backward compatibility matter so much?

A community member posting as @BoboLinNotes flagged compatibility as the release's most practical feature: "The backwards compatibility matters. WordPress plugins tend to stay around for years."

Adams agreed — and acknowledged a real constraint on the protocol side. He responded: "Agreed, and we can't control the backwards-compatibility of the MCP protocol itself, so making a way for this in our ecosystem is important."

That exchange separates two distinct risks for site operators:

• Protocol-level risk: MCP itself is a developing Anthropic standard, and its future backward compatibility is outside WordPress's control.
• Ecosystem-level risk: WordPress plugins routinely stay installed for years, so the adapter is engineered to absorb protocol changes without breaking sites.

Adams's comment is a confirmed engineering statement from Automattic, not speculation — but it also implicitly tells developers and publishers that MCP is still a moving standard, and integrations built today may need to adapt as the protocol evolves.

Who should install it, and how?

The plugin is aimed at two audiences:

• Site owners who want to add AI functionality to their WordPress site using the official adapter
• Plugin developers building MCP support into their own plugins

Version 0.70 is the first release published in the official WordPress.org repository. Users can install it through the standard WordPress admin dashboard or download it directly from the plugin's page on WordPress.org.

The 40,000-plus installation figure predates the directory listing — it accumulated while the plugin was distributed exclusively through the official WordPress MCP Adapter GitHub releases page. That adoption base means the directory launch is a distribution and discoverability milestone rather than a brand-new product debut; the tool has already been running in production environments.

What should site owners watch next?

For publishers and SEO professionals, the official adapter lowers the barrier to making WordPress sites machine-actionable for AI agents — a capability worth monitoring as agentic search and AI assistants expand from retrieving content to performing tasks on sites. Watch for plugin developers adopting the Abilities API pattern Adams described, further directory releases beyond version 0.70, and any signals from Anthropic about how the MCP protocol itself will handle version changes — the one variable Adams admitted WordPress cannot control.