WordPress Releases Canonical MCP Adapter Plugin to Connect AI Agents With WordPress

WordPress has taken another major step toward making websites easier for AI agents to interact with.

On October 7, 2026, the WordPress AI Team announced that its MCP Adapter is now officially available through the WordPress.org Plugin Directory as a canonical WordPress plugin. The current release, MCP Adapter 0.7.0, was released on October 2 and is the first version published through the official plugin directory.

The plugin provides a standardized bridge between WordPress functionality and the Model Context Protocol (MCP), allowing compatible AI agents and AI tools to discover and interact with WordPress capabilities.

This is important because WordPress is not simply adding another AI writing feature. Instead, it is building infrastructure that can allow AI agents to interact with WordPress itself.

What Is the WordPress MCP Adapter?

The MCP Adapter is a WordPress plugin that connects WordPress functionality to the Model Context Protocol, an open protocol designed to allow AI applications to communicate with external tools and systems.

In simple terms, the adapter acts as a bridge:

AI Agent → MCP → WordPress MCP Adapter → WordPress Ability → WordPress functionality

For example, a WordPress plugin could register an ability that retrieves certain information from a website. If that ability is publicly exposed through MCP, a compatible AI agent can discover the ability and invoke it through the MCP interface.

The official WordPress announcement describes the MCP Adapter as infrastructure for exposing WordPress site functionality to AI agents and AI harnesses through MCP.

The important part is that the MCP Adapter does not itself function as an AI chatbot or AI model.

It provides the infrastructure that allows WordPress to communicate with AI systems that support MCP.

What Is MCP?

MCP stands for Model Context Protocol.

It provides a standardized way for AI applications to interact with external tools, resources and capabilities instead of requiring every AI application to build a separate integration for every service.

Think about the problem this way.

Without a common protocol, an AI application wanting to work with WordPress would need a custom integration specifically designed for WordPress.

With MCP, the AI client can communicate with an MCP server using a standardized protocol.

That makes the architecture more like:

AI client → MCP server → application

The WordPress MCP Adapter effectively provides the MCP server infrastructure on the WordPress side.

WordPress previously explained that the adapter allows AI tools such as Claude Desktop, Claude Code, Cursor and VS Code to discover and call WordPress Abilities.

How Does MCP Adapter Work With WordPress?

The key piece connecting MCP with WordPress is the Abilities API.

The Abilities API was introduced in WordPress 6.9. It provides a standardized way for WordPress, plugins and other components to register individual pieces of functionality as “abilities.”

According to the official WordPress documentation, an ability can have:

• A unique name
• A description
• Input and output schemas
• A callback function
• Permission checks
• A defined category

This gives software, including AI agents, a structured way to understand what a WordPress installation can do.

The MCP Adapter then bridges these abilities into the MCP ecosystem.

A simplified example

Imagine a plugin registers an ability called:

store/get-order-summary

The ability could define what information it accepts and what it returns.

The MCP Adapter can make that ability available through MCP.

An AI agent could then discover that capability and, assuming the appropriate authorization and exposure settings are in place, invoke it.

The architecture becomes:

AI Agent
   ↓
MCP
   ↓
WordPress MCP Adapter
   ↓
WordPress Abilities API
   ↓
Plugin / WordPress Functionality

This separation is important because the MCP Adapter does not need to reinvent every WordPress function.

Instead, it provides a standardized connection between existing WordPress abilities and AI agents.

What Can AI Agents Do With WordPress?

The actual capabilities depend on what a WordPress site and its plugins expose.

The MCP Adapter itself does not automatically give an AI agent unlimited access to a WordPress website.

Instead, publicly exposed WordPress Abilities can become discoverable and executable through the adapter’s MCP server.

That opens the door to use cases such as:

• Reading site information
• Retrieving structured WordPress data
• Running plugin-specific functionality
• Automating administrative workflows
• Building AI-powered developer tools
• Connecting ecommerce functionality with AI agents
• Creating custom AI workflows for WordPress
• Allowing AI agents to interact with plugin-defined capabilities

For example, a plugin developer could create an ability for a specific business workflow and expose it through MCP.

The AI agent would then have a standardized way to discover and use that capability.

This is considerably different from simply asking an AI chatbot to generate WordPress code.

Here, the AI can potentially interact with the WordPress environment itself.

MCP Adapter Includes a Default MCP Server

The plugin does not merely provide a protocol library.

The official WordPress MCP Adapter includes a default MCP server.

Its endpoint is:

/wp-json/mcp/mcp-adapter-default-server

The default server provides three fundamental MCP tools for discovering and interacting with WordPress abilities. Developers can also extend the architecture by registering their own tools, resources and prompts.

This gives WordPress developers a common foundation instead of forcing every plugin developer to create a completely independent MCP implementation.

Why Is WordPress Calling It a “Canonical Plugin”?

This is one of the most important parts of the announcement.

WordPress calls MCP Adapter a canonical plugin.

That does not mean that MCP is now part of WordPress Core.

In fact, WordPress has deliberately kept the MCP Adapter outside Core for now.

Why?

The MCP specification is evolving quickly.

The WordPress AI Team explains that a major breaking MCP specification update was released less than three months before this announcement. Because WordPress Core has a strong focus on stability and backward compatibility, the team considers MCP too volatile to put directly into Core at this stage.

Keeping the MCP Adapter as a plugin gives WordPress more flexibility.

The plugin can:

• Update independently from WordPress Core
• Adapt to changes in the MCP specification
• Experiment with new AI capabilities
• Fix compatibility issues more quickly
• Give developers a common implementation
• Avoid multiple competing versions of the same infrastructure

This is particularly useful for an emerging technology such as MCP.

Why Was the Plugin Added to WordPress.org Now?

The MCP Adapter existed before its arrival in the WordPress Plugin Directory.

Earlier versions were primarily distributed through the project’s GitHub repository or as a Composer dependency.

That approach was useful for developers experimenting with the technology, but it was not ideal for normal WordPress administrators.

Publishing the adapter on WordPress.org makes installation and updates considerably simpler.

A WordPress administrator can now find the plugin through the normal plugin ecosystem rather than manually downloading the project or managing the dependency themselves.

WordPress says this distribution also provides a more reliable shared architecture for developers building MCP functionality.

What Is New in MCP Adapter 0.7.0?

Version 0.7.0 is an important release because it is the first version published through the WordPress.org Plugin Directory.

It also adds support for the 2026-07-28 MCP specification.

Some of the changes include:

Support for the 2026-07-28 MCP Specification

The adapter now supports the newer MCP specification revision, including its stateless server/discover behavior and updated HTTP protocol metadata.

The release also maintains compatibility with clients requesting older MCP revisions, which is important because AI clients may not all update their MCP implementations simultaneously.

Elicitation Support

The new version allows directly callable tools to request additional input under the newer MCP specification.

This gives developers more flexibility when a tool needs information before it can complete an operation.

Better Protocol Handling

Version 0.7.0 introduces updated protocol handling and HTTP headers associated with the newer MCP specification.

This is largely developer-facing infrastructure, but it matters because MCP clients and servers need to agree on the protocol version and message structure they are using.

MCP Adapter 0.7.0 Also Has Breaking Changes

Although the release adds new functionality, developers upgrading from earlier versions should not treat it as a completely backward-compatible update.

The official release notes identify several breaking changes.

For example, generated DTO classes and several validation classes were removed. Custom transports also need to use the newer request-handling architecture. WordPress has additionally deprecated using MCP Adapter as a bundled Composer library in favor of installing it as the plugin.

Developers who previously integrated the adapter directly into their own projects should therefore review the 0.7.0 migration guide before upgrading.

For a normal WordPress administrator installing the plugin for the first time, these changes are less significant. They are primarily relevant to developers who have already built integrations around earlier versions.

Is MCP Adapter an AI Plugin?

Not exactly.

This distinction is important.

The MCP Adapter does not provide a complete AI assistant inside WordPress.

It does not give your WordPress dashboard a ChatGPT-style interface.

It also does not include an AI model.

Instead, the plugin provides the server-side infrastructure required for AI systems to interact with WordPress through MCP.

The official announcement explicitly says that the plugin currently focuses on MCP server infrastructure rather than providing an MCP client or a complete end-to-end user-facing AI agent workflow.

So the relationship is better understood as:

MCP Adapter = connection infrastructure

rather than:

MCP Adapter = AI chatbot

What About Security?

Security is one of the most important considerations when allowing AI agents to interact with a website.

An AI agent that can only read public information presents a very different risk from an AI agent that can modify posts, users, orders or other sensitive data.

WordPress’s Abilities API includes permission information as part of an ability’s definition.

The MCP Adapter also does not simply expose every WordPress ability automatically.

The official plugin documentation explains that abilities need to be publicly exposed for MCP access, while permission checks remain active during execution.

This means developers need to think carefully about which capabilities they expose.

A sensible production deployment should follow the principle of least privilege.

For example, a site owner may decide that an AI agent can retrieve site information but should not be allowed to publish content or modify important settings.

The MCP layer does not remove WordPress’s existing authorization model.

Instead, it provides another way of reaching functionality that has been deliberately exposed.

Why This Matters for WordPress Developers

The bigger significance of MCP Adapter is not the plugin itself.

It is the direction WordPress is taking.

The Abilities API gives WordPress a standardized way to describe functionality.

The MCP Adapter provides a standardized way to make that functionality available to MCP-compatible AI systems.

Together, they create a foundation for agentic WordPress applications.

A plugin developer could build a specialized WordPress capability once and potentially make it usable through multiple AI-powered workflows.

That is much more scalable than building a separate custom integration for every AI platform.

What Could WordPress and AI Agents Look Like in the Future?

The long-term possibilities are broader than AI-generated blog posts.

Imagine an AI agent connected to an ecommerce website.

Instead of simply answering:

“How many orders did I receive this month?”

the agent could potentially retrieve the appropriate information directly from WordPress or an ecommerce plugin if the necessary abilities have been implemented and exposed.

Another example could involve website maintenance.

An AI-powered development tool could discover available diagnostic abilities and use them to help investigate a problem.

Content workflows could also become more automated.

For example:

AI agent → WordPress ability → content workflow → draft → human review

The important point is that these workflows depend on the actual abilities made available by WordPress and plugins. MCP Adapter itself does not magically add all these capabilities to every WordPress installation.

WordPress Is Building AI Infrastructure, Not Just AI Features

The MCP Adapter release fits into a broader strategy from the WordPress AI team.

The team’s roadmap for WordPress 7.2 includes work around additional abilities, current MCP implementation, standardized MCP Adapter distribution, easier MCP access and agent identity and delegation. The roadmap also makes clear that these AI features are being developed experimentally and are not guaranteed to become part of WordPress Core in the 7.2 cycle.

That makes the MCP Adapter particularly interesting.

WordPress is effectively creating building blocks for AI agents rather than trying to make one specific AI assistant the center of WordPress.

Should Every WordPress Website Install MCP Adapter?

No.

The release does not mean every WordPress administrator needs to install the plugin immediately.

For a website that has no need for AI-agent integrations, MCP Adapter may provide little immediate benefit.

It becomes much more interesting for:

• WordPress developers
• Plugin developers
• AI application developers
• SaaS developers
• Ecommerce developers
• Agencies building automation workflows
• Businesses experimenting with AI agents

Developers should also remember that the MCP Adapter is still described by WordPress as experimental, with the project currently focused on gathering feedback and working toward a stable 1.0 release.

How to Get MCP Adapter

The plugin is now available through the official WordPress Plugin Directory, making installation much easier than the earlier GitHub/Composer-based workflow.

The current plugin requires WordPress 6.9 or later.

Developers can also follow the project’s source code and release history through the official WordPress MCP Adapter repository on GitHub.

For production websites, however, administrators should understand what functionality they intend to expose before connecting an AI agent.

Final Thoughts

The release of the WordPress MCP Adapter 0.7.0 is more significant than a normal plugin launch.

WordPress is creating a standardized bridge between its own functionality and the growing ecosystem of AI agents.

The combination of the Abilities API and Model Context Protocol gives WordPress developers a way to make site capabilities discoverable and usable by compatible AI systems without building a completely separate integration for every AI platform.

The decision to distribute MCP Adapter as a canonical plugin rather than putting it directly into WordPress Core also makes sense while the MCP specification continues to evolve.

For now, the technology remains experimental. But the direction is clear: WordPress is moving beyond AI-generated content toward a model where AI agents can interact with the capabilities of a WordPress website.

That could eventually change how developers build WordPress plugins, automation systems, ecommerce workflows and AI-powered website management tools.

Frequently Asked Questions

What is WordPress MCP Adapter?

WordPress MCP Adapter is a plugin that connects WordPress capabilities to the Model Context Protocol, allowing compatible AI agents to discover and invoke exposed WordPress functionality.

Is MCP Adapter part of WordPress Core?

No. It is currently distributed as a canonical WordPress plugin rather than being included directly in WordPress Core.

What version is the latest MCP Adapter?

The current release is MCP Adapter 0.7.0, released October 2, 2026.

Does MCP Adapter provide an AI chatbot?

No. The plugin provides MCP server infrastructure. It does not itself provide an AI model or a complete AI assistant interface.

What WordPress version is required?

The MCP Adapter currently requires WordPress 6.9 or later.

Can MCP Adapter modify a WordPress website?

Potentially, but only through capabilities that are actually exposed and authorized. The adapter does not automatically give an AI agent unrestricted access to a WordPress site.

Why did WordPress release MCP Adapter as a plugin instead of Core?

MCP is evolving quickly and has experienced specification changes. Keeping the adapter as a plugin allows WordPress to update the MCP implementation independently without tying those changes directly to the WordPress Core release cycle.