Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

AI & WordPress · Explainer

What Is WordPress MCP? How AI Agents Connect to WordPress

What Is WordPress MCP? How AI Agents Connect to WordPress

Short answer

WordPress MCP refers to connecting WordPress to AI agents through the Model Context Protocol, an open standard for linking AI tools to other software. The official MCP Adapter turns abilities registered with the WordPress Abilities API, added in WordPress 6.9, into MCP tools and resources that assistants such as Claude or ChatGPT can discover and run with permission.

Key takeaways

  • MCP, the Model Context Protocol, is an open standard for connecting AI agents to software.
  • The Abilities API, added in WordPress 6.9, registers what a site can do in a machine-readable way.
  • The official MCP Adapter exposes those abilities as MCP tools, resources and prompts.
  • Abilities are only exposed to MCP when a developer or plugin marks them as available.
  • Treat AI access like any user account: least privilege, authentication and logging.

What is MCP?

MCP, short for Model Context Protocol, is an open standard that lets AI assistants connect to external systems in a consistent way, so one assistant can use tools from many different apps.

The Model Context Protocol website describes MCP servers, which offer tools and data, and MCP clients, which are the AI apps and agents that use them.

Before MCP, every AI integration needed its own custom connection. A shared standard means a WordPress site that speaks MCP can work with many different AI clients.

What does MCP mean for WordPress?

For WordPress, MCP means an AI agent can discover what your site can do, such as reading posts or running a site action, and carry out those tasks through a controlled, documented interface.

Instead of an AI tool guessing how to click through the dashboard, it calls defined functions with clear inputs and outputs. That is more reliable and easier to secure.

Typical uses include drafting and organising content, answering questions about site data, running maintenance checks and helping developers test features. Each of these depends on which abilities the site actually exposes, so two WordPress sites can offer very different MCP tools.

What is the WordPress Abilities API?

The Abilities API is a core WordPress API, introduced in WordPress 6.9, that creates a central registry of things a site can do, called abilities, each with a name, description, input and output schema and permission check.

The Make WordPress AI team's post introducing abilities as WordPress' new functional core explains the idea. Core, plugins and themes can all register abilities.

Because each ability declares what it needs and who may use it, the same ability can be used by the REST API, the command palette and AI agents without rewriting it for each.

What is the WordPress MCP Adapter?

The MCP Adapter is the official WordPress package that translates abilities registered with the Abilities API into MCP tools, resources and prompts, so MCP clients can discover and run them.

The WordPress Developer Blog's introduction to the MCP Adapter describes how it fits into the AI Building Blocks for WordPress initiative.

The adapter is kept outside WordPress core as a plugin, so it can keep pace with fast changes in the MCP specification. Plugins can declare it as a dependency.

The code lives in the MCP Adapter GitHub repository, with documentation and examples for developers.

How does the MCP Adapter expose abilities?

The default MCP server offers three meta-tools to discover abilities, get information about one and execute it, and only abilities marked as public for MCP are available through them.

This layered approach means an AI agent first learns what is available, then reads the details of a specific ability, and only then runs it with the right inputs.

Developers can also create custom MCP servers with their own selection of abilities, for example one server for content tasks and another for store reports.

Does the MCP Adapter add AI features to my site?

No. The adapter is a connection layer; it does not include an AI model or add AI features by itself, and it is only useful when your site has abilities registered by core or plugins.

Think of it as a translator. It lets outside AI tools talk to WordPress in a language they understand, but the actual actions come from abilities.

AI features inside WordPress, such as writing assistants, are separate. They may use the same building blocks but are not required for MCP access.

How do AI clients connect to a WordPress MCP server?

AI clients connect to the site's MCP endpoint over HTTP, or through a local bridge, using an authenticated WordPress user, often with an application password or OAuth, so the agent acts with that user's permissions.

The user account matters. An agent connected with an Administrator account can do everything an administrator can, which is far more than most tasks need.

Create a dedicated user with the lowest role that still covers the task, and revoke its credentials when you no longer use the connection.

Is WordPress MCP safe?

It can be, if you treat AI agents like any other user: expose only the abilities you need, use a least-privilege account, keep credentials secret, log actions and review changes.

The Abilities API helps by requiring permission checks for each ability. A well-written ability refuses to run if the connected user lacks the right capability.

Be cautious with abilities that delete content, change settings or send messages. Keep them off, or require human review, unless you have a clear reason to allow them.

Test new connections on a staging site first. Our guide on setting up a staging site for WordPress shows how to create one.

How is WordPress MCP different from the REST API?

The REST API exposes WordPress data through fixed endpoints for any app, while MCP describes tools in a way AI agents can discover and reason about, built here on the same ability definitions.

You still need the REST API for normal app integrations. MCP adds a layer designed for agents that decide which tool to call based on a task described in plain language.

The WordPress REST API Handbook remains the reference for traditional integrations.

How can developers start with WordPress MCP?

Install the MCP Adapter on a test site, register a simple ability with the Abilities API, mark it as available to MCP, then connect an MCP client and try discovering and running it.

Start with read-only abilities, such as listing recent posts. They are safe to experiment with and show the full flow from registration to execution.

Our step-by-step guide on building a WordPress MCP server walks through the code.

Local development tools are adding MCP support too. Our explainer on WordPress Studio describes how it gives AI coding assistants context about your local sites, which makes experimenting with abilities safer than working on a live site.

What does WordPress MCP mean for site owners?

For site owners, MCP means AI assistants will increasingly be able to help with real site work, such as content updates and reports, through controlled connections instead of copy and paste.

You do not need to adopt it today. Plugins that add MCP support usually keep it off by default, so nothing is exposed until you choose to enable it.

When you do, start small, keep permissions tight and check what the agent changed. The same habits that keep human users safe apply to AI agents too.

Frequently asked questions

What does MCP stand for in WordPress?

MCP stands for Model Context Protocol, an open standard for connecting AI assistants to software. In WordPress, it is used to let AI agents discover and run site abilities through the MCP Adapter.

Is MCP built into WordPress core?

The Abilities API is in core since WordPress 6.9, but the MCP Adapter is a separate official plugin and package, kept outside core so it can keep up with changes in the MCP specification.

Can ChatGPT or Claude edit my WordPress site through MCP?

They can if you connect them to an MCP server on your site and expose abilities that allow edits. The agent acts with the permissions of the WordPress user account used for the connection.

Do I need MCP to use AI with WordPress?

No. Many AI plugins work without MCP. MCP matters when you want outside AI agents or coding assistants to interact with your site through a standard, controlled interface.

How do I keep a WordPress MCP connection secure?

Use a dedicated user with the lowest role needed, expose only necessary abilities, protect credentials, log actions, test on staging first and revoke access you no longer use.

Sources

  1. Model Context Protocol modelcontextprotocol.io
  2. From Abilities to AI Agents: Introducing the WordPress MCP Adapter WordPress Developer Blog
  3. Meet Abilities, WordPress' New Functional Core Make WordPress AI
  4. WordPress/mcp-adapter GitHub
  5. REST API Handbook WordPress Developer Resources

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.