Guide · Technology

WordPress MCP: your options compared

WordPress MCP is a connection that lets an AI assistant, such as Claude or ChatGPT, read and edit a WordPress site. There are three ways to build it: WordPress's own MCP Adapter, a ready-made plugin or a custom-built plugin. The key difference is not the feature list but what the AI is allowed to do on your site, and who decides.

Updated

What is MCP?

MCP, the Model Context Protocol, is an open standard for connecting AI models to external tools and data sources. Anthropic released it in November 2024, and today most AI assistants support it, including Claude and ChatGPT.

In practice, MCP works like a power socket. The site tells the assistant which tools it has (for example "list articles" or "create a draft"), and the assistant uses them when you ask. You can ask Claude which pages are missing a meta description, and it fetches the answer from the site instead of guessing.

The same connection that reads can also write. That is why the most important question is not which plugin to choose, but what the AI is allowed to do on your site.

Three ways to connect WordPress to AI

1. WordPress's own MCP: Abilities API and MCP Adapter

WordPress 6.9 brought the Abilities API into core. It is a shared way of describing what a site can do: each action (ability) has a name, a description, an input and output structure and a permission check. The MCP Adapter is the WordPress project's official package that offers these actions as MCP tools.

The adapter creates a default server that the assistant connects to over HTTP or from the command line with WP-CLI. Authentication uses WordPress's own methods, such as application passwords, so the AI always acts with the permissions of a WordPress user.

Its most important feature is what it does not do: after installation, the AI can do nothing until a plugin or theme has registered actions and they have been explicitly made visible to MCP. Permissions are checked on two levels, for the whole server and for each action.

Fits: an organisation with a developer or partner that wants to build precisely limited AI actions on WordPress's own foundation.

Keep in mind: needs WordPress 6.9 and development work. Automattic's earlier WordPress MCP implementation has been archived, and the MCP Adapter is named as its replacement.

2. A ready-made MCP plugin

There are already dozens of MCP plugins on WordPress.org. Easy MCP AI, for example, is a free plugin that runs on a standard WordPress server without separate services. It offers hundreds of tools for managing content, media, plugins, SEO and analytics.

Permission control is better than many expect. Easy MCP AI supports OAuth and API keys, and for each key you choose which tools are enabled. Tools are grouped into read, write and destructive, and you can require approval for individual tools.

The challenge is volume. With hundreds of tools, the default settings let the AI do almost anything its user can. Limiting that is up to you.

Fits: trying things out, and sites whose administrator wants AI running quickly and is prepared to go through the permissions.

Ask before installing: who develops and updates the plugin, which tools are on by default, whether destructive actions can be removed completely, and whether changes made by the AI are logged.

3. A custom MCP plugin

The third way is a plugin built for your site on top of WordPress's own Abilities API and MCP Adapter. It registers only the actions your work actually needs, such as "create an article draft", "suggest a meta description" or "check for broken links".

The AI cannot see any other actions, so it cannot install plugins, delete content or change users, even if someone tries to mislead it. You can build your own rules into the actions: a draft is always saved as a draft, an image needs alt text, and every change is recorded.

Fits: organisations where many people update the site and the AI should handle recurring tasks in a controlled way, and sites with personal data or business-critical content.

Keep in mind: needs development and maintenance. When WordPress or the MCP Adapter updates, the plugin is tested alongside other updates as part of Care.

Comparison

WordPress's own MCPReady-made plugin (e.g. Easy MCP AI)Custom plugin
What it isAbilities API (in core) and the official MCP AdapterA ready-made plugin that connects assistants to WordPressA plugin built for your site on the Abilities API and MCP Adapter
RequirementsWordPress 6.9+Depends on the plugin, Easy MCP AI: WordPress 6.0+WordPress 6.9+
What the AI can do straight awayNothing until actions are registered and openedHundreds of tools for content, media, plugins and analyticsOnly the agreed actions
AuthenticationA WordPress user, e.g. application password or WP-CLIOAuth or API key, permissions per keyA WordPress user, planned around the use case
Permission controlTwo levels: server and individual actionTools in groups (read, write, destructive), approval optionalDestructive actions absent entirely, your own rules in actions
PriceFreeFreeDevelopment and maintenance
FitsDevelopers building their own actionsTrying out and quick setupControlled production use

Want to connect your site to AI in a controlled way?

We plan the connection, the AI's user and the permissions with you, and test them before production.

Get in touch

What is the AI allowed to do?

Whichever option you choose, ask three questions before connecting.

Who makes the change? Create a separate WordPress user for the AI. Its changes then stand apart from people's, and you can cut the connection by removing one account.

What may it do? Give the least privilege possible. The Editor role is enough for drafts, and the AI does not need administrator rights. Leave out deletions, plugin management and settings.

Where can you see what it did? Make sure changes leave a trace: revision history, a log or at least a separate user. Keep publishing a human decision.

One risk is worth knowing by name: prompt injection. An instruction hidden in a page, comment or email can try to make the assistant do something you did not ask for. Limited permissions are the best protection, because the AI cannot do what it has no tool for.

Test the connection in a staging environment first. More on looking after site security on the page Website security and privacy.

For how work is split between an AI agent and a person in site maintenance, see the guide An AI agent in WordPress maintenance.

Which option fits you?

  • You want to see what AI can do: a ready-made plugin in staging, with read-only access.
  • You want AI to help with content production in production: a custom plugin, or a ready-made plugin limited to drafts.
  • You are building your own actions or integrations: WordPress's own Abilities API and MCP Adapter. The same actions can later serve other systems too.
  • Your site has personal data or many editors: a custom plugin with permissions and rules planned in advance.

Update an older WordPress before connecting in any case. More on WordPress as a platform on the page Technology: WordPress. If AI visibility in search results interests you more than managing the site, read the guide llms.txt and AI search.

Frequently asked questions

Do we need a developer for WordPress's own MCP?

Usually, yes. The MCP Adapter only offers the AI the actions someone has first registered through the Abilities API, and by default they are not visible to MCP. Registering actions, permission checks and testing are PHP development. A ready-made plugin works without code, but then you limit permissions in the plugin's settings.

How is MCP different from the WordPress REST API?

The REST API is WordPress's interface that programs call with exact addresses and parameters. MCP is a layer built for AI: it tells the assistant which tools exist, what they do and what input they expect. Many MCP solutions use WordPress's own functions underneath, so permissions still come from a WordPress user.

Does MCP work on an older WordPress?

WordPress's own MCP Adapter needs WordPress 6.9 or later, because the Abilities API is in core only from that version. Some ready-made plugins already work on WordPress 6.0. If your site is older, update it first anyway, since an old version stops receiving security updates.

What should AI not be allowed to do on a site?

Delete content, install or remove plugins, change users or settings, and publish without human approval. These are the actions where a mistake, or a misled AI, does the most damage. Creating drafts, suggesting meta descriptions and checking content are good first tasks.

Can we try MCP without risk to the live site?

Yes. Connect the AI to a staging environment that copies production first. There you can see which tools the assistant uses and how it behaves before granting any access to production. Clients on our Care service usually have a staging environment ready.

What does an MCP solution cost?

WordPress's MCP Adapter and most MCP plugins are free. The cost comes from setup: planning permissions, creating the AI's user, testing and maintaining it alongside updates. A custom plugin's price depends on how many actions it includes. We estimate it the same way as other continuous development.

Summary

MCP turns AI into a tool for your site, not just someone to chat with. WordPress's own MCP Adapter is the most restricted foundation, a ready-made plugin the fastest way to try, and a custom plugin the most controlled option for production. The choice depends on how much power you give the AI.

If you want to connect your site to AI in a controlled way, get in touch. We handle setup and permission planning as part of Care. More on using AI on websites on the page AI on websites.

Sources

Checked 16 November 2026.

Share this page
  • Glossary

    MCP (Model Context Protocol)

    MCP, the Model Context Protocol, is an open standard for connecting an AI assistant to external tools and data sources, such as a WordPress site, a CRM or a calendar. The system tells the assistant which tools it has, and the assistant uses them on request. Anthropic released MCP in 2024, and most AI assistants now support it.

  • Glossary

    Abilities API

    The Abilities API is a way of describing what a site can do, added to WordPress core in version 6.9. Each action has a name, a description, an input and output structure and a permission check. AI assistants, plugins and other systems can then use the same actions consistently. WordPress's MCP Adapter offers these actions to AI through MCP.

  • Glossary

    AI agent

    An AI agent is an AI assistant that does not just answer a question but works toward a goal: it plans, uses tools and checks the result before its next step. An agent can, for example, list a site's articles, find missing meta descriptions and write drafts for them. Its permissions should be limited, and important actions should need human approval.

  • Glossary

    Prompt injection

    Prompt injection is an attack where instructions are hidden in content an AI reads, such as a web page, a comment or an email, to make the assistant misbehave. The risk grows when the AI has access to systems. The best protection is to give the AI only the tools it needs and to require human approval for important actions.

Want help with your decision?

Tell us your situation. We will get back to you by the next working day at the latest.

Get a priceTell us what you need

Get a price estimate or tell us what you need

The estimate takes a few minutes and does not ask for your contact details. You can also describe your need. We will get back to you by the next working day at the latest.

Get a priceTell us what you need