The WordPress MCP Adapter is now in the WordPress.org plugin directory. Version 0.7.0 landed there on October 2, 2026, published under the WordPress.org name and installable from any WordPress dashboard.
That’s the news a lot of site owners were waiting for. MCP is how AI agents like Claude and ChatGPT talk to software. The MCP Adapter lets them talk to WordPress: find out what your site can do, then do it. Until now, using it meant pulling code from GitHub or Composer. Now it’s a canonical plugin with the WordPress project behind it.
We’re already connecting client sites to Claude, ChatGPT, and other AI tools through the adapter. Here’s what the directory listing changes, what it doesn’t, and the one thing we have every client do before an agent touches production.
What the MCP Adapter does
The MCP Adapter turns a WordPress site into something an AI agent can talk to and act on. It does that by connecting two pieces.
The first is the Abilities API, which landed in WordPress core in version 6.9. An ability is a single, named action your site can perform, like creating a post or listing users. WordPress registers some abilities itself. Plugins can register more.
The second is the Model Context Protocol (MCP), an open standard AI tools use to find and use outside software. Claude, ChatGPT, Cursor, and a growing list of other tools speak it.
The adapter sits between them. An agent connects to your site, asks what abilities are available, reads how each one works, and runs the ones it needs.
What we’re building with it for clients
We’re connecting client WordPress sites to Claude, ChatGPT, and other MCP-capable tools right now. Which one depends on what the client’s team already uses. The adapter doesn’t care, and that’s a big part of its appeal: you aren’t betting your website on a single AI vendor.
Day to day, it looks like this:
- A content team asks Claude to turn interview notes into a post, and it lands in WordPress as a draft with categories, tags, and an excerpt filled in.
- A marketing lead asks ChatGPT which pages haven’t been touched in two years and gets the answer from the site itself, not from last quarter’s export.
- An editor pulls every post that mentions a retired product name and queues them for cleanup.
- A developer’s coding assistant inspects how the site is built before it writes a line of code.
Nobody on those teams had to learn anything technical. They describe the job in plain language. The agent does the clicking.
This is a governance decision, not a plugin decision
Moving to production is where the conversation changes. Once an agent can take actions on your live site, the question stops being “is this cool?” It becomes “what is this thing allowed to do, and who approved that?”
The adapter doesn’t decide what an agent can do. Your site does. The agent can reach whatever abilities are registered and exposed, using the permissions of the WordPress user it connects as. Connect it as an administrator and it has an administrator’s reach.
That list of abilities isn’t fixed, either. Every plugin you install can add to it. A forms plugin might register an ability to export submissions. A commerce plugin might register one to issue refunds. Some abilities delete things permanently.
So the honest answer to “is the MCP Adapter safe?” is that it’s as safe as the decisions you make around it.
The WordPress MCP Adapter plugin is a door. You decide which rooms it opens into.
Write the job description before you hand over the keys
You wouldn’t give a new hire an admin login on day one and say “figure it out.” Treat an agent the same way. Before you turn anything on, write down what it’s for and what it can touch. Here’s the plan we walk clients through.
- Name the jobs. List the two or three tasks you actually want an agent doing. “Draft blog posts” is a job. “AI” is not.
- Inventory what’s exposed. Have your developer list every ability registered on the site. You’ll likely find more than you expected, because plugins add their own.
- Sort every ability into three buckets. Allowed, allowed with a human approving it, and never.
- Give the agent its own WordPress user. Not yours. A dedicated account with the lowest role that can do the jobs. That makes every action traceable and easy to shut off.
- Start on staging. Run the jobs on a copy of the site for a couple of weeks before production sees any of it.
- Log it and review it. Know what the agent did, when, and as whom. Revisit the buckets whenever you add a plugin.
For a typical content team, the buckets end up looking something like this:
| Ability | Our default |
|---|---|
| Read posts, pages, and site settings | Allowed |
| Create a draft post | Allowed |
| Edit an existing published page | Human approval |
| Publish or schedule content | Human approval |
| Upload media | Human approval |
| Delete content | Never |
| Change user roles or create users | Never |
| Install, activate, or update plugins | Never |
Drafting a post? Sure. Changing user roles? Absolutely not. Your list will differ. The point is that you have one, and that someone signed off on it.
Where WebDevStudios comes in
Where we help is the part that’s easy to get wrong. We connect your site to the AI tools your team already uses, whether that’s Claude, ChatGPT, or both. Before anything goes live, we audit which abilities your site actually exposes, including the ones your plugins added quietly. We lock the agent down to the jobs you named, set up the dedicated user and logging, and build custom abilities when the job you want doesn’t exist yet. Then we stay on it as your plugin list changes.
WebDevStudios has built and supported WordPress sites since 2008, for brands like Microsoft, Starbucks, and the NBA. We’ve spent the last year working with AI and WordPress directly. When you work with us on this, you are working with a team dedicated to building and supporting on the WordPress platform. We’ve been doing it for almost two decades!
See the WordPress MCP Adapter in action
Want to watch it happen before you decide anything? We recorded a live demo connecting Claude to WordPress through the MCP Adapter, start to finish:
How to Connect Claude AI to WordPress Using MCP (Live Demo)
If you’d like help with it, talk to us. We’ll go through your site with you, show you which abilities it exposes today, and tell you what we’d turn on first and what we’d never let an agent touch. We’re already doing this for clients on Claude and ChatGPT, and we’d like your team to be next.