If you run a WordPress site and you have heard “MCP” mentioned near “Claude”, you may have filed it under developer things. It is not. It is the single most useful thing that has happened to running a site in years, and this is the explanation for people who own the site rather than build it.
The short version
MCP is a standard that lets an AI assistant use tools. Turn it on in WordPress with AI Engine, connect Claude once, and from then on your site is something you can talk to. Not “generate me a paragraph”. Talk to, as in: “publish last week’s draft”, “find the posts with no description and write one for each”, “which images are not used anywhere”. And it does it, on your actual site, while you watch.
What a site owner actually asks for
These are the things that come up every week and that nobody enjoys doing by hand.
- Publishing housekeeping. “Publish the draft about the summer sale, set the category to News, use the photo I uploaded this morning.”
- The SEO chores. “List every post without a meta description, write one for each in my tone, and show me before saving.” With SEO Engine installed, Claude can also read your Search Console data and tell you which three posts to fix first.
- The media library. “Find images that are not used in any post.” With Media Cleaner, it can run the scan, explain each result, and move the unused ones to the trash, never permanently deleting without you.
- The weekly check. “Anything broken since last week? Any 404s that should be redirects? Any plugin updates I should know about?”
- Content you meant to write. “Take my five bullet points and turn them into a post in the style of my last three articles, as a draft.”
None of that is a chatbot on your site for visitors. This is the assistant working for you, in the back office.
How safe is it
This is the question that matters, and the answer is more reassuring than “AI can edit my site” sounds.
- Claude never runs code on your server. It uses a fixed set of tools: create a post, update a post, list media, and so on. It cannot install things, cannot touch files, cannot reach the database directly. The worst realistic accident is a bad post revision, and WordPress keeps revisions.
- You choose what it can touch. Tools can be limited to reading only, and anything that changes the site can require your approval first. Publishing and deleting are exactly the kind of thing to keep behind an approval.
- It signs in as a real WordPress user, through the normal login screen, so everything it does is logged under that user like any other edit.
- You can disconnect it in one click, and the connection dies with the user’s access.
Setting it up, in three steps
- Install AI Engine. In Meow Apps → AI Engine, open the MCP tab and enable the server. It shows you a connection URL.
- In Claude on your computer, add a connector and paste that URL.
- Claude opens your WordPress login. Sign in, approve, done. No tokens to copy, nothing to paste into a config file.
The developer-flavoured walkthrough, with the details and the bearer token option, is in How To: Connect Claude to WordPress with MCP.
What it costs
Nothing on the WordPress side beyond AI Engine, which is free for this. Claude is your own Claude subscription. There is no per-site fee, no credits, no middleman. If you also want Claude to have SEO and media tools, those come with SEO Engine and Media Cleaner, which register their own tools automatically when installed.
The habit that makes it pay
The owners who get the most out of this treat it like a capable assistant, not a magic button. They ask for a plan before a bulk change. They keep publishing and deleting behind approval. They tell it once when it gets something wrong, and it stops doing that. Within a couple of weeks, the weekly maintenance of a site that used to take an hour takes a five minute conversation.
That is what MCP is for site owners. Not a protocol. A colleague who already knows where everything is.
