Can I Connect WordPress to Claude Code with MCP?

A client asked me recently: “Can I connect our WordPress CMS through my Claude Code MCP?” It’s a fair question, and one I suspect a lot of people are quietly wondering about. AI tools have gone from “write me a paragraph” to “go and do things for me” very quickly, and websites are an obvious next target.

The short answer is yes, you can. The longer answer is that it depends which WordPress you mean, what you actually want it to do, and how comfortable you are handing an AI the keys to your website.

What is an MCP?

MCP stands for Model Context Protocol (which is no more helpful in understanding what it means than the acronym). It’s an open standard that lets an AI assistant, like Claude, talk to other software in a structured way.

The easiest way to picture it is a universal plug adaptor. Out of the box, an AI can only read what you type and write a reply. It can tell you how to publish a blog post, but it can’t actually press the button. MCP is the adaptor that lets it plug into another system and use that system’s buttons directly.

There are always two halves to the arrangement:

• The client is the AI tool you’re using, such as Claude Code, Claude Desktop or claude.ai (other AI agents are available)
• The server is the thing being plugged into, in our case your WordPress website.

The server publishes a menu of things it’s willing to do (“list posts”, “create a draft”, “upload an image”). The AI reads that menu, and when you ask it for something, it picks the right item and asks the server to do it. The important bit: the AI can only do what’s on the menu. Who writes that menu, and what goes on it, turns out to matter a great deal.

First, which WordPress are we talking about?

This trips a lot of people up, and most online guides blur it. “WordPress” can mean two quite different things.

WordPress.com is the hosted service run by Automattic. Since February 2026 it has had an official connector inside Claude. You sign in, approve access, and you’re done. The catch is that it’s read only by default, and needs a paid plan. Claude can look at your stats, summarise comments and audit your content, but it can’t publish anything unless you go into your settings and switch on write tools one by one.

Self-hosted WordPress is what most businesses (and nearly every site I look after) actually run: WordPress installed on your own hosting. Here there’s no single switch. Instead, WordPress itself now ships the building blocks. Version 6.9 introduced something called the Abilities API, and there’s an official plugin called the MCP Adapter that turns those abilities into an MCP menu for Claude to read.

So if someone asks “can I connect WordPress to Claude?”, the honest first reply is: “Which one?”

Why would I want to connect it?

The appeal is simple: you stop copying and pasting. Most people using AI for website content today work in two windows. They draft in Claude, copy it into the WordPress editor, fix the formatting, add the categories, pick an image, and press save. Connecting the two cuts out the middle.

A few situations where that genuinely helps:

• Repetitive admin. Tidying up a messy category list, fixing hundreds of posts with missing image alt text, or finding every page that still mentions an old phone number.
• Getting a quick overview. “Which of our posts haven’t been updated in two years?” is a question that could take ages by hand and seconds for an agent.
• Drafting straight into the CMS. Give it a brief, and bosh – a properly formatted draft appears in WordPress, ready for a human to review.
• Teams that already live in Claude. If your marketing or comms team does most of its thinking in Claude, having the website in the same place removes friction.

Why wouldn’t I want to connect it?

This is the section most “how to connect Claude to WordPress” articles skip (but security is boring when you’re trying to get people to sign up to the shiny shiny).

You’re giving an AI a login to your website. Whatever account you connect with, the AI can do anything that account can do. Connect it as an administrator and, in principle, it can do anything an administrator can. AI tools are good, but they still misunderstand instructions, and they do it confidently. “Clean up the old posts” can mean something very different to you and to a machine.

Some plugins go a long way further than content. A few third-party MCP plugins offer to let the AI run code on your server or edit theme files directly. That’s powerful on a test site. On a live business website, it’s the kind of access we’d normally only give to a trusted developer.

It’s another door into your site. An MCP connection works through your site’s API, protected by a password or token. If that token leaks, or is stored carelessly on someone’s laptop, it’s a route in. Every extra door needs looking after.

It’s still early days. The official WordPress tools are only months old and are moving quickly. Things change month to month, and guides go out of date fast.

You might not need it. If you publish one blog post a month, copying and pasting is fine. Don’t add moving parts to solve a problem you don’t have.

What can it do if I connect it?

Here’s the part that surprises people: with the official self-hosted setup, connecting Claude to WordPress doesn’t, by itself, let it do very much at all.

Remember the menu? With the official MCP Adapter, every ability is private until someone deliberately marks it as public. Once connected, Claude gets just three tools: one to see what’s on the menu, one to read the details of an item, and one to use it. If nothing has been put on the menu, Claude can connect perfectly happily and then do nothing useful.

This means your site decides what the AI can touch, not the AI. Abilities come from WordPress core, from plugins (WooCommerce is already moving its AI features onto this system) or from a developer writing them specifically for your site.

Once the right abilities are in place, typical jobs include:

• Listing, searching and summarising posts and pages
• Creating drafts and filling in categories, tags and SEO fields
• Reviewing comments
• Auditing content: missing images, broken structure, outdated pages
• Looking up products and orders in a shopping context

The third-party plugins take a more “batteries included” approach. Some offer 30 or more ready-made tools for posts, media and settings the moment you switch them on. Quicker to get going, but you’re trusting someone else’s idea of what the menu should contain.

What can’t it do?

It can’t do anything that isn’t on the menu. No matter how nicely you ask, if there’s no ability for “change the homepage layout”, it won’t happen. That’s a feature, not a bug.

It can’t replace judgement. It can draft a post, but it doesn’t know your client relationships, your tone of voice, or that a particular phrase got you into trouble last year (Starbucks…, Tank Day…, South Korea…). Someone still needs to read things before they go live.

It can’t build you a good website from a prompt. You’ll see demos of entire sites “built by AI through MCP”. They’re impressive party tricks. Design, structure, accessibility and performance still need people who know what they’re doing.

It isn’t a way to change how your website is built. This is worth being clear on, because the two are easy to blur. MCP works with the content and settings inside a running site: posts, pages, media, comments. It doesn’t touch your theme or plugin code, and it shouldn’t. Changing the code behind a website is a different job altogether. It needs testing on a staging site, version control so changes can be rolled back, and someone who understands how one change affects everything else. AI can be a useful tool for a developer doing that work, but it’s no substitute for the developer, and it’s certainly not something to point at your live site and hope for the best.

It can’t undo mistakes for you. If it publishes the wrong thing or overwrites a page, you’ll be relying on revisions and backups, just as you would if a person did it.

A word of warning about old tutorials

If you go searching for how to set this up, be careful what you follow. This area has changed so fast that a guide from early 2026 can already be wrong.

The biggest example: Automattic’s original “WordPress MCP” plugin, which many tutorials still recommend, was archived and officially deprecated in January 2026 in favour of the official MCP Adapter. Some guides also tell you to install a separate Abilities API plugin, which isn’t needed now that it’s part of WordPress itself.

A good rule of thumb: if a guide doesn’t mention the MCP Adapter or WordPress 6.9, treat it with suspicion.

So, should you?

I’m going to be about as annoying as I was in the Content Security Policy post here – it honestly depends. If you’re not that bothered about security, quality or reliability, then sure, go for it (that’s not a dig, some people genuinely don’t need to be concerned about these things). If however you’re looking at a production website that generates revenue for your business and gets lots of hits each day, then I would be very, very careful about it.

If you’re curious and do want to give it a go, here’s how I’d approach it:

1. Start on a staging site, never your live website.
2. Use a dedicated account with limited permissions. An Editor, not an Administrator, so the AI can manage content but not plugins or settings.
3. Decide what’s on the menu. Expose only the abilities you actually need, and nothing that touches code or server files.
4. Keep a human in the loop. Let the AI create drafts; let a person press publish.
5. Make sure your backups are solid before you begin, not after.

If you’re not sure, then I’d love to chat it through with you. Drop me an email or schedule a call and I can talk through your options with you.