WordPress’s official MCP Adapter can now be installed from the admin dashboard like any other plugin. On October 7, 2026, WordPress published version 0.7.0 of its canonical MCP Adapter plugin to the WordPress.org plugin directory, the same place you find any standard plugin. According to Search Engine Journal, the plugin had already reached over 40,000 installations through its GitHub releases page before this official listing.
What is the WordPress MCP Adapter?
MCP (Model Context Protocol, an open standard developed by Anthropic) lets AI systems securely connect to external apps, data sources, and tools. For a WordPress site, that means an AI client can discover and invoke site functions, such as publishing posts or working with plugin functions, without custom API code on each end.
The adapter bridges WordPress’s Abilities API (the internal layer that exposes site capabilities to external callers) to the MCP standard, so AI clients can interact with WordPress programmatically. Jason Adams, Director of Engineering, AI at Automattic, announced the release and said the plugin “makes use of the Abilities API to avoid functional redundancy while handling authorization.”
What’s new in version 0.7.0?
Version 0.7.0 is the first release published to the WordPress.org plugin directory and adds support for the MCP 2026-07-28 specification. Key additions, per the GitHub release notes:
- Sessionless server/discover, per-request protocol metadata, and new HTTP headers (
Mcp-Method,Mcp-Name,Mcp-Param-*) under the 2026-07-28 protocol revision - Direct callable tools can now request elicitation input (prompting an AI agent to ask for more information before completing an action) under the 2026-07-28 revision via
McpInputRequired - Clients using earlier revisions (2025-06-18 or 2024-11-05) still connect, served through the 2025-11-25 schema
- Default abilities register even when another plugin initializes the Abilities API first
The release also carries breaking changes for developers who have extended the adapter. According to the GitHub release notes, the generated DTO (data transfer object) classes, the McpToolValidator, McpResourceValidator, and McpPromptValidator classes, and the mcp_adapter_validation_enabled filter have all been removed. Custom transports must now delegate to HttpRequestHandler or McpWireOrchestrator. Using the MCP Adapter as a bundled Composer library (a PHP dependency manager) is deprecated; installing the plugin directly is now the recommended path.
Before you upgrade: quick checklist
- Confirm your site runs WordPress 6.9 or newer (required since v0.6.0)
- If you extended the adapter with custom validators or transports, read the v0.7.0 migration guide before upgrading
- If you bundled the adapter as a Composer library dependency, plan to switch to the standalone plugin install
- If you run multisite and used Streamable HTTP sessions (persistent connections between the server and an AI client), expect those sessions to require one reconnect after upgrading, because session storage moved from network-wide to per-site keys
- If you still run 0.6.0 from the GitHub release ZIP, note that 0.6.1 repaired that ZIP, which could cause a fatal error for plugins calling
class_exists('WP_CLI')
What this means for AI-search visibility
The clearest way to think about this: most AI tools today read your website like a visitor would, by fetching your HTML. MCP changes the model. A site with MCP enabled gives AI agents a structured, action-oriented interface to request data and trigger functions directly. That is a different kind of discoverability than traditional search crawling.
In Hingewise’s view, the move to the WordPress.org directory matters as much as the technical upgrade. Previously, MCP on WordPress required locating and installing a GitHub release, a step that effectively limited adoption to developers. A standard admin-dashboard install removes that barrier for the broader site-owner base. Adoption is likely to grow meaningfully faster from here.
The backward-compatibility design is also worth noting as a strategic signal. The MCP specification itself is evolving quickly, this single release references four protocol revisions (2024-11-05, 2025-06-18, 2025-11-25, and 2026-07-28). A canonical plugin that handles multi-version compatibility at the platform level reduces the maintenance burden for every plugin developer building on top of it. That structure is likely to accelerate how quickly MCP-aware capabilities spread through the WordPress plugin ecosystem.
For brands thinking about AI-search presence: the question worth asking is whether your site’s content and data are accessible to AI agents in structured form, not just crawlable as HTML. MCP is one emerging answer to that question. Whether AI search platforms will weight MCP-connected sites differently in their responses is not yet established, the protocol is still maturing, but the infrastructure is moving into place.
Sources: Search Engine Journal, Oct 7, 2026; GitHub, WordPress/mcp-adapter Releases
Lam Nguyen · Hingewise
This article was drafted with AI assistance from the sources cited above and checked against them before publishing. The "What this means for AI-search visibility" section is Hingewise's editorial analysis, built on the frameworks and positions we use in our GEO work. How we work: Editorial policy.