WordPress MCP: How I Use AI Agents to Run My WordPress Sites (2026)

I run three WordPress sites, and I was tired of doing the same chores by hand on each one. Fix a meta description here, create a redirect there, moderate comments on all three.

So I built an MCP server that lets an AI agent do it for me. Now I tell Claude Code "audit the SEO on these posts and fix the gaps," and it works through them across every site.

That is the whole shift: you stop clicking through wp-admin and start describing the job.

This is what WordPress MCP is, how the official version and self-hosted ones differ, and exactly how I use it day to day.

What is WordPress MCP?

WordPress MCP is a way to let an AI agent read and manage your WordPress site through safe, defined tools, instead of you clicking through wp-admin. The "MCP" part is the Model Context Protocol, an open standard for connecting AI assistants to outside tools and data.

In plain terms: the AI does not get a login and free run of your dashboard. It gets a fixed menu of actions, "create a post," "update SEO title," "add a redirect," and can only do what is on that menu.

That framing matters. It is the difference between handing someone your keys and handing them a remote with clearly labelled buttons.

Is there an official WordPress MCP?

Yes, and this is the big shift. WordPress 6.9 shipped an official MCP Adapter, built on a new Abilities API, so AI tools can discover and call WordPress functions directly.

So the ecosystem now has three layers, and "which is best" depends on where you sit:

• The official MCP Adapter is the core protocol layer. It is the safe default for standard WordPress abilities and the foundation everything else builds on.
• Automattic's server is the path for WordPress.com hosted sites.
• Self-hosted proxies (the kind I built) sit on top for people who want a deep, opinionated tool set across several self-hosted sites.

They are not really competitors. The official adapter is the plumbing. A proxy is a set of power tools bolted onto it.

What can an AI agent actually do with it?

A lot more than post. The proxy I run exposes 46 tools across the parts of WordPress you actually touch, each one a specific, permissioned action.

Because each tool is typed and named, the agent knows exactly what it can call. There is no "type a command and hope." That is what makes it safe to point at a live site.

How does it work under the hood?

Two pieces, and no OAuth dance. It is deliberately simple, so you can audit every part.

A Python MCP proxy (built on FastMCP) speaks the protocol to your AI client and holds the tool definitions. A small WordPress must-use plugin exposes the matching REST endpoints on each site. The two talk over the REST API, authenticated with an application password, which WordPress has supported natively since 5.6.

Multi-site is the part I lean on most. A single sites.json file lists every site and its application password, and each tool call carries a site parameter. Add or remove a site by editing that one file. No restart, no redeploy.

How do you set it up?

Three steps, once. You need Python 3.10+, the uv package manager, and WordPress 5.6 or newer. The full code and setup guide live in the GitHub repo.

The SEO layer, and teaching the agent your rules

The tools I use most are the SEO ones, and they run on Rank Math. Through it, the agent reads and writes titles, meta descriptions, focus keywords, canonicals, robots directives, Open Graph and Twitter cards, schema type and the primary category, the same fields I would set by hand.

There is one more piece that makes the agent genuinely useful rather than generic: a skills package. It teaches the agent each site's own rules, its E-E-A-T requirements, meta-tag conventions and internal-linking style, so the output matches the site instead of reading like stock AI text.

Install it with npx skills add 5unnykum4r/wordpress-mcp. This is the same discipline I write about in meta tags for WordPress and getting cited in ChatGPT and Perplexity, just handed to the agent as instructions it follows every time.

What I actually use it for

Not novelty demos, real maintenance that used to eat my week. A few examples from the last month.

• SEO audits at scale. I ask the agent to find posts with a missing meta description or no focus keyword across all three sites, then fix them in a batch. What was an afternoon of clicking is now a single request.
• Content refreshes. It pulls an old post, updates the stale parts against current facts, tightens the SEO fields, and leaves it for me to review before publishing.
• Redirects and moderation. New 301s go in through the redirect tools instead of a plugin UI, and comment moderation across sites happens in one pass.
• Heavier automation. For multi-step jobs I wire it into Grip AI, my open-source agent platform, so the agent can run a whole workflow rather than one action at a time.

Is it safe to give an AI agent access to your site?

It is as safe as you scope it, and safer than sharing a login. Three things keep it in check.

Connections use application passwords, not your real password, and you can revoke any one of them in seconds. The agent can only call the defined tools, so it cannot run arbitrary code. And because it runs locally under your control, you decide which sites go in sites.json and you approve what happens.

Treat the destructive tools (delete, bulk status) with the same care as any admin action, and it is a calmer way to work than clicking through three dashboards.

Final take

WordPress MCP is the moment WordPress management stops being manual clicking and becomes something you can delegate. WordPress made it official in 6.9, and the self-hosted tools push it further for people running several sites.

I built mine because I wanted my own sites run to my own standards without doing every step by hand. If you manage more than one WordPress site, this is the workflow shift worth trying, carefully, on a staging site first.