The official bridge connecting the WordPress Abilities API with artificial intelligence agents has reached a critical milestone. MCP Adapter version 0.7.0 has officially landed in the WordPress.org plugin directory, bringing full compatibility with the July 2026 Model Context Protocol (MCP) revision. However, this major update introduces strict validation rules and deprecates bundled library distributions, sending ripples through developer ecosystems worldwide.

Released in October 2026 and spearheaded by core contributors Ovidiu Galatan and David Levine alongside the official WordPress.org maintenance team, the plugin has surged past 40,000 active installations. Tested and verified for compatibility up to WordPress 7.1.2, the tool is rapidly becoming a foundational cornerstone for sites looking to seamlessly integrate with advanced AI agents like Claude, ChatGPT, and custom LLM workflows.

1. Main Facts: What’s New in MCP Adapter 0.7.0?

The transition to version 0.7.0 represents a significant technical leap forward for how WordPress talks to artificial intelligence. At its core, the MCP Adapter translates registered WordPress core and plugin "abilities" into standard tools, resources, and prompts that external AI agents can discover and execute securely.

The headline feature of this release is native support for the MCP 2026-07-28 protocol revision. This update overhauls the fundamental handshake and communication paradigms between WordPress sites and AI clients:

• Stateless Discovery: Traditional connection sequences relying on initial initialize and ping handshakes have been complemented by a stateless server/discover request.
• Granular HTTP Headers: Incoming HTTP requests now require explicit protocol metadata, including headers such as MCP-Protocol-Version, Mcp-Method, and Mcp-Name.
• Caching and Status: Responses now include granular caching and status directives, such as resultType and ttlMs (Time-To-Live in milliseconds), optimizing performance for high-traffic headless architectures.
• Backward Compatibility: Support for the preceding 2025-11-25 session-based HTTP specification remains intact. Older clients requesting legacy revisions (2025-06-18 or 2024-11-05) continue to be served via their respective schemas.
• Interactive Elicitation: Under the new revision, AI tools can prompt human users for additional data mid-execution using the novel McpInputRequired mechanism.

Furthermore, version 0.7.0 rectifies a frustrating race-condition bug where default core capabilities failed to register properly if a third-party plugin initialized the underlying Abilities API prematurely.

2. Chronology of the Project: From Experimental Bridge to Official Plugin

To understand the weight of the 0.7.0 release, it is helpful to trace the rapid evolution of the Model Context Protocol within the WordPress ecosystem.

• Late 2024 – Early 2025: As large language models shifted from passive chat interfaces to active agents capable of executing code and managing software, the WordPress community recognized an urgent need for a standardized API layer. The concept of the "Abilities API" took shape, providing a unified way to expose site functions securely.
• Mid 2025: The initial iterations of the MCP Adapter emerged on GitHub as an experimental repository. Developers began utilizing Composer to bundle the adapter directly inside custom plugins, using Jetpack Autoloader to prevent conflicts.
• August 2026: The project faced growing pains, notably requiring an emergency patch (version 0.6.1) to rectify a corrupted distribution ZIP file that triggered fatal errors on staging environments. Despite these hurdles, adoption skyrocketed as agencies rushed to build AI-driven editorial workflows.
• October 2, 2026: Version 0.7.0 drops. For the first time, the adapter bypasses purely GitHub-based distribution and takes its place in the official WordPress.org plugin directory. This shift marks its graduation from an experimental developer tool to a mainstream infrastructural component of the CMS.

3. Supporting Data and Technical Metrics

The adoption metrics and architectural footprints surrounding the MCP Adapter paint a clear picture of an enterprise-ready technology experiencing rapid maturation:

• Active Installations: Exceeding 40,000 live sites globally.
• Core Requirements: Requires WordPress 6.9+ and PHP 7.4+, with complete test validation up to WordPress 7.1.2.
• Protocol Support Matrix:
  • 2026-07-28: Fully supported (stateless, metadata-driven headers).
  • 2025-11-25: Supported (session-based HTTP).
  • Legacy Revisions (2025-06-18, 2024-11-05): Maintained for backward compatibility via STDIO (WP-CLI) and legacy routes.
  • Batch Requests: Strictly rejected across all supported revisions.
  • Deprecated Methods: The legacy tools/list/all method has been permanently deprecated and removed.

4. Official Responses and Migration Guidelines

The release notes and accompanying developer migration guide issued by Galatan and Levine emphasize structural rigor. While standard end-users who simply install the plugin and declare basic abilities will notice a frictionless transition, developers extending the plugin face a stark reality: strict schema enforcement has replaced auto-correction.

The End of Auto-Correction

In previous versions (v0.6 and earlier), the adapter acted as a benevolent safety net. If a developer registered a tool, resource, or prompt with malformed icons, flawed metadata, or invalid argument annotations, the adapter silently cleaned up the data behind the scenes.

Version 0.7.0 strips away this leniency:

• Zero Tolerance for Schema Violations: If a component fails to match the strict schema requirements of either supported protocol revision, it is rejected entirely, and WordPress throws a standard _doing_it_wrong() debugging notice.
• JSON-RPC Error Responses: If an execution function returns data that violates its declared output schema, the connected AI client immediately receives a standard JSON-RPC error code (-32603). Consequently, poorly written custom tools that worked fine in v0.6 may suddenly vanish from AI clients after updating.

Developer API Changes

For developers building advanced integrations or custom transports, the breaking changes are substantial:

• Generated DTO classes, along with specific validators (McpToolValidator, McpResourceValidator, McpPromptValidator), have been completely excised.
• Utility classes like McpValidator and ContentBlockHelper have been streamlined or removed, alongside the deprecation of the mcp_adapter_validation_enabled filter.
• Server getter methods now strictly require explicit schema declarations with no default fallbacks.
• Custom transport layers must now delegate directly to HttpRequestHandler or McpWireOrchestrator.
• List filters (such as mcp_adapter_tools_list) now accept the active schema as their third argument, and all core WP-CLI integration classes have been declared final.

5. Implications for the WordPress Ecosystem

Beyond protocol updates and code refactoring, version 0.7.0 delivers a decisive blow to an entrenched distribution pattern: bundled Composer dependencies.

Farewell to Bundled Libraries

Historically, plugin authors frequently bundled their own private copies of the MCP Adapter library via Composer, leveraging the Jetpack Autoloader to prevent version collisions. Version 0.7.0 officially deprecates this practice.

The adapter now issues persistent runtime warnings if it detects a bundled copy coexisting with the official WordPress.org plugin. The core team’s recommended path forward is clear:

1. Remove the private Composer dependency using composer remove wordpress/mcp-adapter.
2. Rely on Composer’s standard autoloader.
3. Declare a formal plugin dependency in the main plugin header: Requires Plugins: mcp-adapter.
4. For optional integrations, developers are advised to use conditional checks like class_exists( 'McpAdapter' ) rather than forcing hard dependencies.

Best Practices for Production Environments

Given that the MCP Adapter remains within the 0.x semantic versioning lifecycle—where breaking changes can occur across minor version bumps—site administrators must exercise caution.

Experts strongly advise against updating production environments blindly. Administrators should test the upgrade on a staging site first, verifying that all AI-driven workflows and tools remain visible within their chosen MCP client (such as Claude Desktop or custom enterprise interfaces). Furthermore, site managers are reminded to keep their WordPress installations fully patched—particularly in light of recent critical security hardening seen in releases like WordPress 7.1.2.

As artificial intelligence agents become first-class citizens in content management workflows, the standardization brought by MCP Adapter 0.7.0 ensures that WordPress remains at the absolute forefront of the AI revolution, demanding higher standards of code hygiene and architectural resilience from its developer community.