WordPress and MCP: Letting an AI Assistant Manage Your Site

Connecting an AI assistant directly to your WordPress site is possible now. How hard it is depends almost entirely on which WordPress you run.

The technology is called MCP, and the distance between the easy path and the hard path is wider than anything else I have looked at this year.

This is a different thing from the AI features built into WordPress itself, which live inside the editor. MCP lets an assistant work on the site from outside it.

I built MCP support into a small product of my own earlier this year, so I have seen both ends of it: what it takes to expose something to an assistant, and what it actually feels like to work that way.

What MCP actually is, in plain terms

MCP stands for Model Context Protocol. Strip the name away and it is a standard way for an AI assistant to use a tool rather than only read about one.

Without it, you copy your content into Claude or ChatGPT and copy the answer back out. With it, the assistant has an address for your site and a list of things it is permitted to do there. Ask it to find every post missing alt text, and it goes and looks.

The important part is what it does not get. The assistant is not handed your password and does not log into your dashboard as you. It receives a scoped set of actions, and you decide what goes on that list.

That distinction is the entire security model.

On WordPress.com it is close to a toggle

If your site is hosted on WordPress.com and you are on a paid plan, this is genuinely easy.

You enable MCP access in your account settings, choose whether assistants get read access or read and write, and then connect the assistant. Claude, ChatGPT and Cursor all have official connectors, so the connection happens through a sign-in screen rather than a configuration file.

Authorisation uses OAuth 2.1, so your WordPress.com password is never handed to the AI client at all. What it receives is a token, and you can revoke it from the same settings screen without changing anything else.

The surface it opens up is broad. Posts, pages, plugins, themes, users, site settings, media, comments and taxonomies, across more than sixty separate actions.

There is no plugin to install for any of it.

On a self-hosted site it is still a project

If you run your own WordPress, the picture changes completely.

The official tool is the MCP Adapter, built by the WordPress AI team. It works, and it is well made. It is also distributed through GitHub releases rather than the plugin directory, so there is no searching for it under Plugins, then Add New.

More to the point, it has no settings screen. Connecting an assistant means creating an application password, then editing a configuration file inside your AI client with your site address, a username and that password. Some setups route it through WP-CLI on the command line instead.

The set of actions available out of the box is also small today. The richer create-and-update abilities are still being written.

So my honest read is this. If editing a configuration file is not something you want to be doing on a Tuesday evening, wait. This path is not finished for a general audience yet, and there is no cost to letting it land properly.

The plugins filling the gap

Predictably, third-party plugins moved into that space quickly. They fall into three groups:

• all-in-one plugins that bundle a visitor chatbot and an MCP server together
• MCP servers scoped to one job, such as a store or a form builder
• hosted connectors sold as a managed service with a monthly fee

Two are worth naming. AI Engine ships an MCP server alongside its chatbot, and switching it on is a checkbox rather than a configuration file. WooCommerce has its own official MCP integration, which is where I would start if the thing you actually want to manage is a store rather than a blog.

The trade is identical in every case. You get a toggle instead of a configuration file, and in exchange you are trusting a third party with write access to your site.

One thing to watch for. The original Automattic WordPress MCP plugin has been archived in favour of the official adapter. Any guide still pointing you at it is out of date, and it is no longer receiving security fixes.

What it is genuinely good for

The jobs worth handing over have a recognisable shape:

• finding every post missing alt text and fixing them in one pass
• auditing which plugins are still active and which have gone stale
• turning a pile of rough notes into a draft that lands in your editor
• tidying categories and tags that drifted over several years

Bulk, boring and reversible.

That last word carries the most weight. The tasks worth delegating are the ones where a mistake costs you an undo rather than an apology.

Publishing is not on my list. Drafting is.

Give it the smallest account that works

If you do connect something, the setup matters more than which assistant you picked:

• Make a separate user. Create a dedicated account for the assistant rather than pointing it at your own administrator login.
• Give it the lower role. Editor is enough for content work, and an assistant that cannot install plugins cannot install a bad one.
• One password per tool. Application passwords are created individually, so a separate one for each assistant means you can revoke one without breaking the others.
• Start read-only. Let it look around for a week before it is allowed to change anything.

None of that is paranoia. It is the same instinct that stops you handing a new contractor every key on their first day.

Final thought

I like MCP a great deal, and I still think most people running their own site should wait a release or two.

On WordPress.com it is ready now and worth ten minutes of an evening. Self-hosted, the official path assumes a comfort with configuration files that most site owners reasonably do not have, and the third-party shortcuts ask for a level of trust I would want to sit with first.

If you want to try it with no risk at all, connect it read-only and ask it to describe your own site back to you. What it gets wrong tends to be more useful than what it gets right.