Contents
The WordPress MCP Adapter is the official plugin from the WordPress team that lets Claude (and other AI assistants) read and act on a WordPress site, without any copy-pasting. It connects in minutes, but it exposes almost nothing until you decide otherwise, and one default setting deserves your attention before you turn it on.
I see SME leaders torn between "a free plugin I found on YouTube" and "a developer for six months". There is a shorter path, as long as you understand what the adapter brings and what it deliberately leaves out.
- 🔑 Official plugin, a project from the WordPress Core AI team, available in the plugin directory.
- 🎯 Abilities required, the adapter only exposes the capabilities you declare, nothing more.
- ⚠️ Default permissions, left unchanged, any logged-in account can reach the MCP server.
- 🚀 My verdict, adopt it for one specific use case, on a backed-up site, with drafts reviewed.
What does the WordPress MCP Adapter actually do?
The WordPress MCP Adapter is a plugin that turns WordPress "abilities" into tools, resources and prompts for the Model Context Protocol (MCP), the open standard that connects AI assistants to a company's tools. It contains no artificial intelligence of its own: it is simply a bridge between Claude and your site.
Why all the talk of "abilities"?
Since WordPress 6.9, the Abilities API lets WordPress and plugins declare what they can do, each with a unique name, a typed input and output schema, and a permission check. According to the WordPress Developer Blog (February 2026), the adapter turns these abilities into MCP primitives so that clients such as Claude Desktop, Claude Code, Cursor or VS Code can discover and call them.
How is the adapter different from plain REST API access?
The REST API gives broad access that Claude has to learn to handle. The adapter, by contrast, presents named, controlled actions. I covered the REST route in detail in Claude WordPress API: connect it without breaking your site; the two approaches complement each other, with REST being the rawer of the two.
An adapter exposes what you declare. A REST API exposes everything the user is allowed to do.
For context on the protocol itself, my take on whether to adopt it is in Should you really adopt MCP (Model Context Protocol)?.
How do you connect Claude to WordPress with the adapter?
Connecting Claude to the WordPress MCP Adapter takes three steps: install the plugin on a site running WordPress 6.9 or later, declare the abilities you want to expose, then configure the Claude client to point at the site's MCP server. Allow an hour for a first trial on a test site.
What are the installation steps?
According to the plugin's listing on fr.wordpress.org, you install it via Plugins > Add New, search for "MCP Adapter", then activate it. A single WP-CLI line also does the job: wp plugin install mcp-adapter --activate. According to the GitHub repository, the adapter supports two transports, HTTP and STDIO, and can run several MCP servers side by side.
Next, you register the abilities to expose, or install a plugin that registers them for you. Without that step, according to InstaWP's analysis, a fresh install exposes only three gateway tools and three read-only abilities from WordPress core.
And on the Claude side?
The Claude client (Desktop or Code) is configured with the server address and credentials. For a site that is publicly accessible, the safest approach is a dedicated user with limited permissions and an application password, as I show in the REST API article. The Developer Blog covers both scenarios, local environment and public site.
A video tutorial from the WebSensePro channel offers a consumer-friendly variant: download the adapter from the GitHub "releases", then add a small single-file plugin to make the connection easier. The result on screen: Claude creates an SEO-optimised blog post directly on the site. I like the idea, not the method: a plugin of unknown origin adds an attack surface that the official adapter does not have.
Official adapter or Easy MCP AI: which should you choose?
For an SME, the official adapter is the right fit when you want strict control over every action, and Easy MCP AI is the right fit when you want a ready-made catalogue of tools. Both are free, but they solve different problems.
What extra does Easy MCP AI offer?
According to the Juliano channel, Easy MCP AI runs directly on your WordPress install, with no third-party cloud server, and offers 232 tools, an audit log of every call and a before/after history so you can roll back. Jitendra Vaswani's channel cites more than 280 tools and connections to six SEO plugins and six analytics tools. The two figures don't match, and I won't pick a side: the catalogue changes from one version to the next.
Juliano also compares it with WP Vibe, one of the first WordPress MCPs, which is good but paid. On a tight budget, the fact that Easy MCP AI is free counts for a lot.
| Option | Price | Tools exposed | Choose it when |
|---|---|---|---|
| Official MCP Adapter | Free | 3 gateways + declared abilities | You want strict control and have a developer available |
| Easy MCP AI | Free | 232 to 280+ depending on the video | You want a ready-made catalogue with built-in auditing |
| WP Vibe | Paid subscription | Not specified in the sources | You prefer a managed service |
| REST API + application password | Free | Everything the user can do | One-off needs, drafts only |
SOURCE: cited transcripts (Juliano, Jitendra Vaswani), fr.wordpress.org · UPDATED Nov 2026
When is the alternative the better choice?
If your need is "publish posts with the SEO fields filled in", Easy MCP AI gets you there faster, because the tools already exist. The official adapter pulls ahead as soon as several people have access to the site, or an auditor asks you to justify every permission. My conviction: a useful assistant that does one specific job beats a catalogue of 232 tools of which you use three.
What security risk do you need to fix before enabling the adapter?
The first thing to fix is the MCP transport permission: without a custom callback, according to InstaWP's analysis, the adapter only checks the "read" capability, which every logged-in account has, down to a basic subscriber. A single filter raises that bar, and you need to apply it.
What happens if a permission is badly written?
Again according to InstaWP, a permission check that crashes or returns an error blocks the request, which is the right behaviour. The real danger is a callback that wrongly returns "true", because that is never logged. You won't see anything, which is why you should start on a test site.
Why do automatic updates matter?
The same article notes that the adapter, which reached 0.7.1 on 16 October 2026, is still pre-1.0 and had passed 60,000 active installs by 5 November 2026. A pre-1.0 plugin can change behaviour on update: pin the version on your clients' sites.
There is also the deeper issue of malicious instructions hidden in the content the AI reads, which I covered in Claude and prompt injection: a 1% failure rate is already too much. An agent that reads visitor comments and has the power to publish is exactly the case to watch.
This reflex follows the principle of least privilege that ANSSI, France's national cybersecurity agency, recommends in its IT hygiene guides, available on cyber.gouv.fr: an account gets only the permissions its task requires, no more, no less.
Connecting Claude to WordPress without backups or human review just means automating mistakes faster.
Another promising use: Imran Siddiq (Web Squadron) shows the adapter being used to diagnose a site, for example a 500 error after a plugin update. This isn't content creation, it's troubleshooting, where the AI reads a lot and changes little. In my view, that is the best entry point, because the risk stays low.
My verdict: should your SME adopt it?
Yes, for a specific, measurable use case, on a backed-up site, with drafts that someone reviews before publication. No, if you just want to "put AI on the site" without knowing which task you're trying to speed up. My test is simple: where does your team lose time in WordPress?
Where should you start?
I would start with a repetitive task: blog post drafts, filling in SEO tags, or a broken-link audit. Measure the time saved over two weeks before expanding. If you'd rather have it installed and locked down by an expert, you can describe your needs to AI First: an AI expert builds it and a human checks it.
FAQ
Is the WordPress MCP Adapter free?
Yes, it is an open-source plugin available in the official WordPress directory. Any costs come from your Claude subscription and your hosting, not from the plugin itself.
Which version of WordPress do I need?
According to InstaWP's analysis, the adapter requires WordPress 6.9 or later and PHP 7.4, because it relies on the Abilities API introduced in WordPress 6.9. An older site needs updating first.
Can Claude publish directly to my site with the adapter?
Technically yes, if you declare a publishing ability and the logged-in user's permissions allow it. I recommend limiting Claude to drafts, reviewed by a person before anything goes live.
What's the difference between the MCP Adapter and Easy MCP AI?
The official MCP Adapter is a transport layer that only exposes the abilities you declare. Easy MCP AI is a full plugin that provides more than 200 tools out of the box, plus an audit log of every call.
Do I need a developer to install it?
Installing the plugin is well within reach of any WordPress administrator. Declaring custom abilities and setting transport permissions, however, requires some PHP knowledge, which makes a developer's help worthwhile.
Vidéos YouTube
- How To Connect Claude AI to WordPress via MCP (Step-by-step) — WebSensePro
- I Tested Easy MCP AI: The FREE WordPress MCP Server With 242 Tools — Juliano
- Use MCP Adapters to Check and Fix your WordPress Sites — Imran Siddiq, Web Squadron
- Easy MCP AI WordPress Plugin Review — Jitendra Vaswani
