WordPress published its MCP Adapter plugin on wordpress.org
WordPress published MCP Adapter 0.7.0 on wordpress.org, serving two MCP schema revisions and exposing WordPress abilities as MCP tools to AI agents, with 40,000 active installs carried over from the GitHub distribution.
Image: WordPress.org
Why it mattersA team building an AI agent against WordPress sites now has an official server-side endpoint with named protocol revisions, so the integration does not break when another plugin bundles a different adapter version.
The way AI agents will talk to WordPress sites is now a WordPress.org plugin, not a floating GitHub project. WordPress published MCP Adapter 0.7.0 to wordpress.org, and the Search Engine Journal piece that drew attention to it is right about one thing: this is the version a plugin developer should depend on from now on.
The plugin takes WordPress abilities, which are single capabilities registered by WordPress core or a plugin, such as reading posts or updating a setting, and exposes them to AI agents through Model Context Protocol. The adapter does the server and transport work: HTTP and STDIO are both built in, protocol negotiation and permission checks run through the adapter, and the Abilities API provides the actions themselves.
What the version 0.7.0 release actually changes
The 0.7.0 release serves exactly two MCP schema revisions, 2025-11-25 and 2026-07-28. Clients that propose the older 2025-06-18 or 2024-11-05 revisions still connect, and the adapter negotiates them down to 2025-11-25. The 2026-07-28 schema adds a sessionless server/discover lifecycle, elicitation input (so a tool call can ask the user for a value before it runs), and a per-request immutable context object with schema, transport and session data.
The release also removes a generation layer: DTO classes and validator classes are gone, and wire validation now runs through the selected schema instead. Invalid protocol fields are rejected rather than silently dropped. Custom transports must delegate to a specific orchestrator class, and JSON-RPC batch requests are no longer accepted.
The release notes list 0.7.0 under "Breaking changes" for a reason, and the 0.7.0 migration guide on the project's GitHub is where plugins that already bundle an older adapter version will want to start.
What a site owner and a plugin author each get
An ability is only reachable over MCP if it has been marked public, and WordPress permission checks still run against the current user before any tool executes. That is the sentence to send to a security reviewer: an agent is a user, and the same permission model that governs humans governs the agent. There is no shortcut.
Jason Adams, Director of Engineering for AI at Automattic, told Search Engine Journal that the adapter cannot control the backwards-compatibility of the MCP protocol itself, which is why handling multiple revisions at the server is the point of a canonical adapter at all. Plugin developers can now declare Requires Plugins: mcp-adapter in their plugin header and stop bundling their own copy.
40,000 active installations carried over from the earlier GitHub distribution. WordPress 6.9 or newer is required, and the plugin is marked tested up to 7.1.3.
Source
Primary: MCP Adapter 0.7.0 on wordpress.org. Press: WordPress Releases Canonical MCP Adapter Plugin, Search Engine Journal.
This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.
Get AI News in your inbox
New developer tools, model and agent releases, and how teams are actually using them to release software. Short, and only when there is something worth reading.