MCP is how AI assistants like Claude and ChatGPT stop chatting and start working on your WordPress site. Short, honest answers to what everyone actually asks.
New here? MCP for WordPress is the gentle intro. Below, the real questions, answered straight.
The Basics
What even is MCP?
USB-C for AI. It is an open standard that lets an assistant actually do things on your site instead of just talking about them. One port, every tool.
What can it actually do on my site?
Anything you would do in wp-admin, by asking. Draft posts, fix SEO, clean out junk media, translate, pull your traffic numbers. You talk, it does the clicking.
Can I build a whole site with it from scratch?
More than you would think. Point an assistant at a clean install and it will scaffold pages, menus, images and content. It will not replace a developer on a big custom build, but it goes far. I run live sites built almost entirely this way.
What site owners actually ask it to do
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.” It works with the SEO plugin you already use: Yoast SEO, Rank Math, All in One SEO, SEOPress, The SEO Framework or Slim SEO. 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.
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.
Plugins
Is there an official WordPress way to do MCP?
Yes. WordPress 6.9 shipped the Abilities API, 7.0 built on it, and the official MCP Adapter exposes it over MCP. It is developer-grade plumbing; plugins wrap it with logins and a real interface.
So which plugin should I use?
It depends on how you want to connect. The main options today:
- The official MCP Adapter: the cleanest base if you are a developer.
- AI Engine (ours): free, no account, no daily cap (the facts). Your assistant connects straight to your site and signs in with OAuth (read-only is an option), and no password is stored anywhere else. It also brings a chatbot, AI forms and image generation. In our own side-by-side test, the same read task in Claude took 15 seconds, against 26 through a cloud relay.
- WPVibe (from the SeedProd team): a cloud relay with a genuinely smooth onboarding, and an official ChatGPT app that works on free ChatGPT plans. It needs an account, the free plan stops at 100 tool calls a day (paid plans from $99 a year), and connecting sends a full-admin application password to their servers. AI Engine vs WPVibe: the facts.
- Easy MCP AI (Themeisle): free and self-hosted, but its tool list weighs about 63,000 tokens, against about 8,000 for AI Engine, and every conversation pays for that in speed and cost.
Whichever you pick, read the next answer first.
How do I spot a junky AI plugin?
MCP is this year’s gold rush, and a lot of plugins are marketing with some code bolted on. A big tool count and a shiny page prove nothing. Look for a real changelog, fast support, and a team that obviously uses the thing. You are handing an AI the keys to your whole site. Trust beats hype, every time. I wrote down my whole checklist in Vibecoding with WordPress.
Connecting
Which AI tools can connect?
Claude, ChatGPT, Cursor, VS Code, Gemini, n8n, and the list keeps growing. Set it up once and they all work. That is the whole magic of a shared standard. In Claude, AI Engine for WordPress is in the directory: click Connect, sign in to your site, approve. In ChatGPT, AI Engine for WordPress ↗ is in the plugin directory: click Install plugin, sign in to your site, approve. To connect your own site directly, with every tool and nothing in between, use Developer mode, on paid plans.
What’s the coolest thing to connect?
Mix WordPress with other MCP servers, like GitHub, Slack, Notion, or a browser through Playwright, and an assistant can turn a GitHub issue straight into a published post. Just stick to official servers; plenty of community ones ship with no security at all.
What’s my site’s MCP URL?
Depends on the plugin, each has its own. AI Engine’s, for example, is /wp-json/mcp/v1/http. Check your plugin’s MCP settings for the exact one.
OAuth or API key?
Chat apps like Claude and ChatGPT: OAuth, just sign in and approve. Dev tools and automations: a token. Any decent plugin does both.
It won’t connect. What’s wrong?
Nine times out of ten, it is not the plugin. It is a local-only URL, a host or firewall blocking the path, or a login that quietly failed. Go outside-in: is the site public, does the endpoint answer, does the auth pass? (On AI Engine, there is a full troubleshooting guide.)
Step-by-step guides for each assistant
- Claude: the Claude app in one click, Claude Desktop and claude.ai, or Claude Code in the terminal.
- ChatGPT: the plugin directory, or Developer mode on paid plans.
- OpenCode: a 100% free setup with a free model.
- OpenClaw: your own always-on agent.
- Workspace: our free app to talk to your site from your phone.
- Fix: MCP connection issues: when the connection won’t go through.
Trust, Cost & Models
Is it actually safe?
It can be, if you respect what it is. You are giving an AI real power, so scope it: a limited role, read-only when you can, revoke anytime. Test on staging first. Treat it like a new hire, not a magic button.
- 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. Installing plugins or touching theme files and the database are separate Pro tools, which a Content or Read-only connection can’t use.
- Every change can be undone. AI Engine keeps a 30-day history of what each assistant changed: undo it in one click in AI Engine → MCP (Recent Changes), or just ask “undo what you just did”. Trashed posts and comments come back too. Only what WordPress deletes for good (media files, categories and tags) can’t.
- Deletions can wait for you. With Ask Before (AI Engine → MCP → Access), the assistant needs your approval before deleting anything, or before any site change. New installs start with deletions. Drafts Only lets it write and edit drafts without ever publishing.
- You choose what it can touch. When you connect an assistant, an admin approves it once with Full, Content or Read-only access, and you can switch it to Read-only or revoke it anytime in AI Engine → MCP → Connections. Starting with Read-only is a good idea.
- 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.
Should I connect directly, or through a service?
The safest setup is your AI talking straight to your own site: nothing in between, no password stored anywhere else. Some services work as a relay instead. Every request and every answer goes through their servers, and connecting gives them a full-admin password to your site. WPVibe works this way. It is made by Awesome Motive, the company behind WPBeginner, which is why you see it recommended so often. Its free plan stops at 100 actions a day, then it is from $99 a year.
A relay is not wrong in itself, but if that company is ever breached, sold, or changes its rules, it already holds the keys. Our own connector for ChatGPT and Claude is also a relay: it is free with no daily cap, it never stores your WordPress password, and the content of your requests passes through without being logged or stored (we only keep usage counts). If you can, connect directly. Whatever you choose, ask your chatbot of choice to compare the options, and give the least access you can to companies you do not know well.
Will it leak my data?
Whatever the AI reads goes to whoever runs it (Anthropic, OpenAI, and so on). The MCP server is just the pipe. Expose less, sleep better.
Does it cost anything?
MCP is free and open, and most servers are free or already inside a plugin you own. The only bill is the AI itself, your Claude or ChatGPT usage.
Does the AI model matter?
Not to MCP. It is model-agnostic. Claude, GPT, Gemini, even a local model, they all speak the same protocol.
What does matter: every model has a knowledge cutoff, so it may not know the newest WordPress release or this week’s security fix. MCP for WP is a free MCP server we run that keeps your assistant current on WordPress versions, security releases and the right docs. It only knows WordPress; AI Engine is what lets your assistant work on your site.
Got one we missed? Ask us, and we will keep this fresh as MCP keeps moving. 😺
