WordPress MCP: What Is the Model Context Protocol? (2026 Guide)

If you have been following WordPress development lately, you have probably seen the term MCP popping up everywhere. With WordPress 7.0 launching on April 9, 2026, MCP support is one of the headline features. But what does it actually mean for your site?

Let me break it down without the jargon.

What Is MCP?

The Model Context Protocol (MCP) is an open standard created by Anthropic in late 2024 that defines how AI applications talk to external tools and data sources. Think of it like USB for AI: before USB, every device needed its own proprietary cable. MCP does the same thing for AI integrations — it provides one universal interface so any AI assistant can connect to any compatible service.

In December 2025, Anthropic donated MCP to the Agentic AI Foundation under the Linux Foundation, co-founded with Block and OpenAI. It has since been adopted by every major AI provider including Google DeepMind. This is not a niche experiment — it is becoming the industry standard.

MCP defines four core primitives:

• Tools — executable actions the AI can call (like publishing a post)
• Resources — passive data the AI can read (like your site settings)
• Prompts — reusable templates that guide specific workflows
• Sampling — lets servers request AI completions back through the client

How MCP Works in WordPress 7.0

WordPress does not implement MCP directly in core. Instead, the approach is two-layered:

1. The Abilities API (introduced in WordPress 6.9) lets plugins, themes, and core register standardized, discoverable, typed, and executable capabilities.
2. The MCP Adapter plugin bridges those abilities to the MCP protocol, so AI clients like Claude Desktop, Cursor, or VS Code can discover and call them.

WordPress 7.0 also ships the WP AI Client in core — a provider-agnostic API that lets any WordPress code call generative AI models through a consistent interface. You manage AI providers through a new Settings > Connectors dashboard in wp-admin.

The result: AI tools connect to your WordPress site via MCP, discover what your site can do through the Abilities API, and execute actions — all with proper authentication and permissions.

What Can AI Do With Your WordPress Site?

Once MCP is set up, an AI assistant can interact with your site the same way a human admin would, but faster. Some practical examples:

• Content generation — draft posts, suggest titles, or rewrite paragraphs directly in the editor
• SEO suggestions — analyze your content and recommend improvements based on your site data
• Image optimization — process and compress media without manual intervention
• Analytics queries — ask natural-language questions about your site traffic and get answers
• WooCommerce automation — update product descriptions, adjust pricing, or generate reports via MCP tools
• Site diagnostics — check runtime info, plugin conflicts, and performance metrics

The key point: the AI does not get unrestricted access. Every action goes through WordPress permission checks.

The Abilities API Explained

The Abilities API is the foundation that makes all of this possible. Each ability requires four things:

• A unique identifier in namespace/ability-name format (like core/get-site-info)
• Input and output schemas with typed data structures
• A permission callback that enforces WordPress user capabilities
• An execute callback that performs the actual work

WordPress ships three core abilities out of the box: core/get-site-info, core/get-user-info, and core/get-environment-info. Plugins can register their own.

To make an ability available to MCP clients, developers add a meta.mcp.public flag during registration. Without this flag, the ability stays internal — giving developers explicit control over what AI agents can access.

The MCP Adapter itself provides three bridge abilities: mcp-adapter/discover-abilities, mcp-adapter/get-ability-info, and mcp-adapter/execute-ability. These let AI clients explore and use everything your site exposes.

How This Differs From Wix and Squarespace

Both Wix and Squarespace have built-in AI features — Wix ADI can generate entire sites, and Squarespace offers AI-powered text and image generation. These work well, but they are closed systems. You get exactly what the platform provides, nothing more.

WordPress takes the opposite approach with MCP. Instead of building specific AI features into the platform, WordPress provides an open foundation that any AI tool can plug into. The trade-offs:

• WordPress + MCP: more flexible, works with any AI provider, extensible through plugins, but requires more setup
• Wix/Squarespace AI: works immediately, polished user experience, but locked to whatever AI features the platform decides to ship

If you are building a simple personal site, built-in AI is convenient. If you are running a business or want to choose your own AI tools, WordPress and MCP give you that freedom.

How to Prepare Your Site

WordPress 7.0 launches April 9, 2026. Here is how to get ready:

1. Update to WordPress 7.0 once it drops. Make a full backup first.
2. Check your hosting — confirm your host supports PHP 8.1+ and has updated their WordPress environment.
3. Install the MCP Adapter plugin from the official WordPress/mcp-adapter repository.
4. Configure AI Connectors under Settings > Connectors in wp-admin. You will need API keys from your preferred AI provider.
5. Review plugin compatibility — major plugins like WooCommerce and Yoast are already building Abilities API support. Check your installed plugins for updates.
6. Test on staging first — especially if you run a production store or membership site.

Frequently Asked Questions

Is MCP free to use?

Yes. MCP is an open standard under the Linux Foundation. The WordPress MCP Adapter is also free and open source. You will need API keys from an AI provider, which may have their own pricing.

Does MCP give AI full control of my site?

No. Every MCP action goes through the WordPress permission system. AI agents authenticate with application passwords and can only perform actions that the authenticated user is allowed to do. Developers must explicitly flag abilities as MCP-accessible.

Which AI assistants work with WordPress MCP?

Currently supported clients include Claude Desktop, Claude Code, Cursor, and VS Code with the appropriate MCP extensions. Any MCP-compatible client can connect.

Do I need WordPress 7.0 to use MCP?

The Abilities API was introduced in WordPress 6.9, so you can start experimenting now. However, WordPress 7.0 brings the WP AI Client into core and adds the Connectors UI, making the setup much easier.

Will my existing plugins work with MCP?

Existing plugins continue to work as before. To expose their functionality to AI agents via MCP, plugin developers need to register abilities with the Abilities API. Many popular plugins including WooCommerce are already adding support.