WordPress MCP Adapter: when WordPress talks to AI agents

What changes with WordPress 6.9

WordPress 6.9 introduces theAbilities API - a layer that makes WordPress functionality standardized, discoverable, typed, and executable. Each "ability" is a concrete action WordPress can perform, with a permissions system and an execution callback.

At the same time, the WordPress team is publishing an official MCP Adapter . MCP (Model Context Protocol) is the protocol created by Anthropic that lets AI agents communicate with external services. The adapter bridges the two: it exposes WordPress abilities as MCP tools that any AI agent can discover and call.

In other words: Claude Code, Claude Desktop, VS Code, or Cursor can now interact directly with a WordPress site - reading information, executing actions, all in a secure and standardized way.

The Abilities API in brief

A WordPress "ability" is a function registered with:

• A unique identifier - for example core/get-site-info
• A permissions callback - which determines whether the current user has the right to execute this ability
• An execution callback - the business logic itself
• A parameters schema - for typing and validating inputs

This design is familiar if you know WordPress's REST API, but with one key difference: abilities are discoverable by AI agents, not just by HTTP clients.

The default abilities

WordPress 6.9 ships with three core abilities:

These three abilities are a starting point. Plugin and theme developers can register their own abilities - for example: creating a post, modifying an option, running an export, analyzing performance.

The MCP Adapter: how it works

The MCP Adapter is an official package that installs into a WordPress plugin. Once activated, it:

1. Automatically discovers all registered abilities
2. Exposes them as MCP tools via a built-in MCP server
3. Handles authentication - the AI agent must identify itself as a WordPress user with the right permissions

The MCP protocol supports several transports (HTTP, stdio). The adapter uses the Streamable HTTP transport by default, which lets remote AI agents connect via a URL.

Which AI agents are compatible?

All MCP clients work. The official article gives configuration examples for:

• Claude Desktop - configuration in the MCP settings
• Claude Code - via the config .claude.json where the command /mcp
• VS Code - via the Claude extension where the MCP settings
• Cursor - via the built-in MCP configuration

Once connected, the agent can query WordPress: "What are the site's details?", "Which user am I?", and execute any registered ability it has permission for.

Concrete use cases

The MCP integration opens up new workflows for WordPress developers:

• Assisted debugging - asking Claude Code to fetch the site's environment info to diagnose an issue
• Content generation - an agent that creates draft posts directly in WordPress from a brief
• Automated auditing - an agent that checks the site configuration, permissions, active plugins
• Maintenance - running admin tasks (clearing the cache, updating options) without opening the dashboard

The key point: everything goes through the WordPress permissions system. An agent can only do what the authenticated user can do - nothing more.

Security and permissions

Security is central to the design:

• Each ability has a permissions callback checked before execution
• The AI agent must authenticate as a WordPress user (application passwords, OAuth, etc.)
• Abilities are only exposed if the MCP Adapter plugin is explicitly activated
• The developer chooses which abilities to register - nothing is exposed by default beyond the three core abilities

It's an "opt-in" model: you decide what the agent can do, not the other way around.

Why this matters

WordPress powers more than 40% of the web. The fact that the core team is officially adopting MCP means that:

• The MCP protocol is gaining legitimacy outside the Anthropic ecosystem
• WordPress developers can start thinking "AI-first" in their plugins
• The gap between no-code/low-code tools and agentic AI is narrowing - a non-developer could operate a WordPress site through an AI agent

It's also a strong signal for other CMSs and web frameworks: native MCP integration is likely to become a standard.