On October 7, 2026, the WordPress Core AI team announced that WordPress MCP Adapter 0.7.0 is available as a canonical plugin in the WordPress.org Plugin Directory. The experimental plugin provides a default MCP server for WordPress sites and a shared path for AI assistants to discover and call publicly exposed site capabilities. The announcement by Nik McLaughlin outlines the release and its current limits. ([make.wordpress.org](https://make.wordpress.org/ai/2026/10/07/the-mcp-adapter-plugin-is-now-available-on-wordpress-org/))
For developers evaluating how to connect WordPress functionality to AI agents, the practical takeaway is that the adapter now has a standard directory installation and server endpoint. This article explains what 0.7.0 provides, how it connects to the Abilities API, and what to consider before using an experimental release. ([make.wordpress.org](https://make.wordpress.org/ai/2026/10/07/the-mcp-adapter-plugin-is-now-available-on-wordpress-org/))
WordPress MCP Adapter 0.7.0 is an experimental server plugin, not a complete AI-agent interface. It exposes a default server at /wp-json/mcp/mcp-adapter-default-server, bridges publicly exposed WordPress Abilities to MCP, and lets developers register custom servers. It does not include an MCP client or a user interface for agent workflows. ([make.wordpress.org](https://make.wordpress.org/ai/2026/10/07/the-mcp-adapter-plugin-is-now-available-on-wordpress-org/))
What WordPress MCP Adapter adds
The plugin connects WordPress site functionality to the Model Context Protocol (MCP), a format AI assistants and other clients can use to discover and interact with capabilities. Its default server includes three fundamental MCP tools and offers a common starting point for developers building integrations. ([make.wordpress.org](https://make.wordpress.org/ai/2026/10/07/the-mcp-adapter-plugin-is-now-available-on-wordpress-org/))
The server endpoint is /wp-json/mcp/mcp-adapter-default-server. The adapter also supports custom tools, resources and prompts, while developers can register their own MCP servers through the mcp_adapter_init hook. That gives plugin authors a choice: extend the default server or create a server for a more specific integration. ([make.wordpress.org](https://make.wordpress.org/ai/2026/10/07/the-mcp-adapter-plugin-is-now-available-on-wordpress-org/))
How the Abilities API connection works
WordPress MCP Adapter bridges MCP with the Abilities API, introduced in WordPress 6.9. Publicly exposed Abilities on a site can be discovered and executed through the default server’s tools. The adapter therefore provides a protocol connection; what an assistant can do depends on the Abilities the site makes available. ([make.wordpress.org](https://make.wordpress.org/ai/2026/10/07/the-mcp-adapter-plugin-is-now-available-on-wordpress-org/))
That distinction matters for developers planning an integration. The adapter does not automatically turn every site feature into an agent action. Developers still need to expose the relevant functionality as Abilities, and decide which capabilities should be publicly available. The announcement describes the bridge and public exposure, but does not claim the plugin includes a site-specific set of agent workflows. ([make.wordpress.org](https://make.wordpress.org/ai/2026/10/07/the-mcp-adapter-plugin-is-now-available-on-wordpress-org/))
What changed in version 0.7.0
Version 0.7.0 supports the stateless MCP specification dated 2026-07-28. Clients requesting the 2025-06-18 or 2024-11-05 specifications can still connect; the release notes say they are served through the 2025-11-25 schema. Direct callable tools can also request elicitation input under the 2026-07-28 specification with McpInputRequired. ([make.wordpress.org](https://make.wordpress.org/ai/2026/10/07/the-mcp-adapter-plugin-is-now-available-on-wordpress-org/))
The release also changes when default Abilities register: they now register even if another plugin initializes the Abilities API first. Developers upgrading from an earlier GitHub or Composer installation should check the 0.7.0 migration guide before changing an existing integration. ([make.wordpress.org](https://make.wordpress.org/ai/2026/10/07/the-mcp-adapter-plugin-is-now-available-on-wordpress-org/))
Why the adapter is a canonical plugin
Before the directory release, developers got the adapter through GitHub or Composer. That meant manually installing it or managing it as a dependency in project code. A WordPress.org listing makes installation more direct and gives plugin developers a shared canonical version to build against, rather than relying on separate copies that may conflict or fall behind. ([make.wordpress.org](https://make.wordpress.org/ai/2026/10/07/the-mcp-adapter-plugin-is-now-available-on-wordpress-org/))
The announcement also explains why the adapter is not part of WordPress core: the MCP specification is changing quickly, and keeping the adapter outside core lets it track that work on a different release schedule. The directory listing allows other plugins to require it through plugin dependencies, a feature introduced in WordPress 6.5. That can make the adapter available as a dependency without placing MCP functionality in every WordPress installation by default. ([make.wordpress.org](https://make.wordpress.org/ai/2026/10/07/the-mcp-adapter-plugin-is-now-available-on-wordpress-org/))
What the plugin does not include
MCP Adapter focuses on server infrastructure. It ships no MCP client and no user interface for an end-to-end agent workflow. A site owner installing it should not expect a built-in chat panel or an assistant that connects and acts on its own. The plugin supplies the server side that compatible clients and integrations can use. ([make.wordpress.org](https://make.wordpress.org/ai/2026/10/07/the-mcp-adapter-plugin-is-now-available-on-wordpress-org/))
The release remains experimental. The team says it is gathering developer feedback while working toward a stable 1.0 release. For teams testing it now, that status is a reason to review the project’s documentation and migration guidance, test integrations in an appropriate environment, and share feedback through the project’s GitHub issues. ([make.wordpress.org](https://make.wordpress.org/ai/2026/10/07/the-mcp-adapter-plugin-is-now-available-on-wordpress-org/))
WordPress MCP Adapter FAQ
Where is the default MCP server endpoint?
The endpoint is /wp-json/mcp/mcp-adapter-default-server. The plugin’s default server includes three fundamental MCP tools and can expose public WordPress Abilities through its tools. ([make.wordpress.org](https://make.wordpress.org/ai/2026/10/07/the-mcp-adapter-plugin-is-now-available-on-wordpress-org/))
Does MCP Adapter include an AI assistant or client?
No. The plugin provides server infrastructure, but it does not include an MCP client or a user interface for a complete agent workflow. A compatible client or separate integration is needed to connect to the server. ([make.wordpress.org](https://make.wordpress.org/ai/2026/10/07/the-mcp-adapter-plugin-is-now-available-on-wordpress-org/))
Is version 0.7.0 ready for production?
The WordPress AI team labels the plugin experimental and says it is collecting feedback on the way to a stable 1.0 release. Developers should assess that status against their own integration requirements and test before adopting it on a live site. ([make.wordpress.org](https://make.wordpress.org/ai/2026/10/07/the-mcp-adapter-plugin-is-now-available-on-wordpress-org/))
Developers building MCP integrations for WordPress can review the 0.7.0 documentation and migration guidance, then test the default endpoint with the Abilities their site intends to expose.