Matt Mullenweg approved MCP as a de facto part of the WordPress experience (AI contributor meeting, 21 October), and the AI team aims to propose MCP for core in 7.3.
Expect MCP support to become standard; build on abilities and the MCP Adapter rather than custom endpoints.
The MCP Adapter (official WordPress plugin, not part of core) turns abilities into MCP tools, resources and prompts. Abilities are private by default: set meta.public or meta.mcp.public to true (an explicit meta.mcp.public => false overrides meta.public => true). The default server offers three meta-tools (mcp-adapter/discover-abilities, mcp-adapter/get-ability-info, mcp-adapter/execute-ability) at /wp-json/mcp/mcp-adapter-default-server, or over STDIO with wp mcp-adapter serve --server=<id> --user=<user>.
Register an ability with meta.public => true and install the MCP Adapter plugin. Always pass --user to wp mcp-adapter serve: without it, STDIO runs unauthenticated.
Session initialization data is now limited to 4 KiB to prevent oversized data from causing repeated database failures; affected clients must reconnect once. In 0.7.1, an ability not exposed through MCP returns ability_not_found instead of ability_not_public_mcp.
Update to MCP Adapter 0.7.1 (or 0.6.2 for Composer users on 0.6.x) and stop matching on ability_not_public_mcp.
MCP Adapter 0.7.0: new MCP spec, now a WordPress.org plugin
Adds MCP revision 2026-07-28 (older clients are served through 2025-11-25) and is the first release in the WordPress.org plugin directory. Breaking: the generated DTO classes, McpToolValidator, McpResourceValidator, McpPromptValidator and the mcp_adapter_validation_enabled filter were removed, and custom transports must delegate to HttpRequestHandler or McpWireOrchestrator.
Install MCP Adapter as a plugin; bundling it as a Composer library is deprecated. Read the v0.7.0 migration guide before upgrading extensions.