Last Tuesday I published a post, cleared a plugin-update backlog, and pulled a list of every draft older than 90 days on a client site — without opening wp-admin once. I typed requests into Claude in plain English, and the WordPress MCP adapter handled the rest. Total time: about eleven minutes, most of it me reading before approving.
The plumbing behind this shipped with WordPress 6.9, when the official MCP Adapter landed — and almost everything written about it so far assumes you build plugins for a living. This wordpress mcp tutorial is the other version: for site owners and agencies who want to connect Claude to WordPress, run real maintenance in plain English, and keep tight control over what the agent is allowed to touch.
In this guide
What WordPress MCP actually does
MCP — the Model Context Protocol — is an open standard that lets an AI assistant discover and call tools on another system. Instead of Claude guessing at your site through a browser, your WordPress install advertises a menu of typed capabilities: create a post, list plugins, update a term, run a query. Claude picks the tool, WordPress enforces the permissions. If the protocol itself is still fuzzy, my plain-English primer on MCP servers for website owners covers it in ten minutes.
The practical difference from the old REST API workflow is discovery. With the REST API, you (or a developer) had to know every endpoint and wire it up by hand. With the MCP adapter, Claude reads the tool list at connection time and figures out the rest. That is why a non-developer can now do a wordpress mcp server setup in an afternoon — the hard integration work moved into the protocol.
Step 1: Install the MCP adapter
Requirements first: WordPress 6.9 or newer (the adapter builds on the Abilities API that shipped alongside it), a site served over HTTPS, and an administrator login. Five minutes of prep saves an hour of debugging.
- Update core. Dashboard → Updates. If you are on 6.8 or earlier, the adapter has nothing to plug into.
- Install the adapter. Plugins → Add New, search for the official WordPress MCP Adapter, install, activate. Exact menu labels may shift a little between releases — the flow does not.
- Confirm the endpoint. The adapter exposes an MCP endpoint on your domain. Note the URL from the plugin’s settings screen; you will paste it into Claude shortly.
On my test sites this took under four minutes. The only failure I have hit was a security plugin blocking the new endpoint — allowlist it and move on.
Step 2: Create a scoped token
Do not connect Claude with your admin account. Create a dedicated user — I name mine claude-agent so the audit trail is unmistakable — and give it the Editor role, not Administrator. Editor covers posts, pages, and media, which is 90% of what you will actually delegate. Then generate an Application Password for that user (Users → Profile → Application Passwords). WordPress shows the token once; store it in your password manager, because you will never see it again.
This one decision does more for your security than everything else in this guide combined. An Editor-scoped token cannot install plugins, edit theme files, or create admin users — so even a badly worded prompt, or a compromised laptop, has a hard ceiling on the damage it can do.
Step 3: Connect Claude Desktop or Claude Code
Both clients work; they suit different people. Claude Desktop is the point-and-click route — add a connector, paste your site’s MCP endpoint and token, restart, done. Claude Code is the terminal route: one claude mcp add command with the same URL and token. I use Desktop for content work and Code for anything that touches multiple sites, because Code makes it easy to script the same request across a whole roster.
Either way, run the same smoke test: ask Claude to “list my five most recent drafts.” If it returns real titles from your site, the connection works end to end. If it errors, the culprit is almost always the token (retyped wrong, or the spaces stripped) or a security plugin blocking the endpoint — those two account for every failed setup I have walked people through.
Real tasks to run first
Skip the party tricks. These five requests are where an AI agent managing a WordPress site earns its keep in the first week:
- Draft and stage a post. “Write a 600-word update announcing our new pricing, save as draft, assign the News category.” You review in wp-admin, then publish. Claude drafts; you stay on the button.
- Content audit. “List every post older than 18 months that has no internal links pointing to it.” This used to be a spreadsheet afternoon. Now it is one sentence.
- Bulk metadata cleanup. “Find posts missing a meta description and draft one for each, under 160 characters.” Review the batch, approve, done.
- Comment triage. “Summarize the pending comments and flag anything that looks like genuine customer feedback rather than spam.”
- Plain-English queries. “Which categories have had no new posts this quarter?” The agent reads; you decide.
Notice what is not on the list: nothing destructive, nothing that publishes without review. That is deliberate — and if you want to see how far the drafting side scales, my experiment on whether Claude can build a website from a blank server pushes it to the limit.
Scope what the agent can touch
Every horror story about AI agents and websites traces back to the same mistake: full admin access on a production site on day one. Here is the containment checklist I use on client installs.
- Least privilege, always. Editor role for content work. Upgrade to Administrator only for a specific task, then downgrade again the same day.
- Drafts by default. For the first month, instruct Claude to save everything as a draft. Publishing stays a human click.
- Staging before production. Point the connector at a staging copy first and let it run for a week. A proper dev/stage/prod pipeline makes this trivial.
- Rotate and revoke. Application Passwords can be revoked per-token without touching the user’s real password. Rotate quarterly; revoke the moment a laptop or contractor leaves the picture.
- Backups before plugin work. If you do grant update rights, take a backup first and update one plugin at a time. Boring beats broken.
Hosting that won’t fight your agent
Your host decides whether this workflow feels effortless or like wading through mud. Aggressive bot filtering, no staging, or an opaque platform API will all get in the agent’s way. Three roster picks, from my own sites:
Kinsta is what I run this exact setup on — Google Cloud C2 machines behind Cloudflare’s enterprise tier, and a clean platform API that plays well with automation on top of the MCP layer. Entry plans run ~$30–35/mo at the time of writing. I have gone deep on that pairing in my Kinsta API + Claude automation guide.
WP Engine has the best staging workflow in managed WordPress — true dev/stage/prod environments, which is exactly where you want an agent living during its probation period. EverCache keeps the front end fast while the agent works, and entry pricing sits around ~$20–25/mo. If you use their Smart Search AI, my Smart Search setup walkthrough pairs naturally with an MCP connection.
On a budget, Hostinger at ~$3–12/mo is a perfectly sane place to run your first experiments — spin up a throwaway WordPress install, connect Claude, and break things where it does not matter. Graduate to managed hosting when the agent graduates to production. The full rankings live in my best AI web hosting pillar.
Frequently asked questions
Do I need to know how to code to use WordPress MCP?
No. The adapter installs like any plugin, and Claude Desktop connects through a settings screen. The only vaguely technical step is pasting a token into a config field. Claude Code users type one command. If you can install a caching plugin, you can do this.
Is it safe to let an AI agent manage my WordPress site?
Safe is a spectrum you control. With an Editor-scoped token, drafts-by-default, and a staging site for anything risky, the blast radius is small — smaller, honestly, than handing wp-admin credentials to a new freelancer. With a full admin token on production and no backups, it is not safe at all. The tooling is neutral; the scoping is the safety.
What is the difference between the WordPress MCP adapter and the REST API?
The REST API is the plumbing; MCP is the directory on top of it. REST endpoints require someone to write integration code for each task. The MCP adapter describes your site’s capabilities in a format AI assistants understand natively, so Claude discovers what it can do the moment it connects — no custom code, no middleware.
Can Claude update plugins through MCP?
Only if the connected user has permission to — which is exactly why I recommend starting with an Editor role that cannot. When you are ready to delegate updates, grant the capability deliberately, back up first, and have the agent update one plugin at a time rather than all sixteen at once.
Want the guided version? Our free courses walk you through this start to finish — including “Launch Your First Website with Claude.”