WordPress MCP: let Claude build, edit, and manage WordPress for you
A WordPress MCP server lets Claude create sites, write real Gutenberg content, and manage wp-admin, ReDock ships one on localhost:47200, free.
WordPress MCP means exposing a WordPress site — or a whole fleet of local sites — as tools that an AI agent can call directly. Instead of you clicking through wp-admin while the AI describes what to do, Claude Desktop, Claude Code, or Cursor calls the tools itself: create a site, install a plugin, write a page in real Gutenberg blocks, log in, verify the result. ReDock is a free native macOS app that ships this today: the entire app is an MCP server on localhost:47200.
What MCP actually changes for WordPress
The Model Context Protocol (MCP) is an open standard for connecting AI clients to tools. Before it, “AI + WordPress” mostly meant pasting generated text into the block editor by hand. The model wrote; you operated the software.
With an MCP server in front of WordPress, the agent operates the software. It can:
- create and start a full WordPress site (PHP, MySQL, install — one provisioning step)
- author posts and pages as structured Gutenberg blocks and patterns, not raw HTML
- install and activate plugins and themes
- read and write the database, with audit trails and undo hints
- open wp-admin through a single-use magic login link — no stored passwords
- share the running site through a Cloudflare tunnel, or deploy it
Every one of those is a tool call the agent makes and can verify. That verification loop — write, then read back — is what separates an agent from an autocomplete.
Why local-first matters here
An agent with write access to a production site is a liability. An agent with write access to a local site is a workflow.
ReDock runs everything on your Mac. Each site gets a real https://name.test domain with a locally trusted certificate, its own pinned PHP version, and its own MySQL database. Nothing the agent does touches a live server until you deliberately share or deploy it. If Claude rewrites your homepage badly, you’re one revision away from undoing it — on a site nobody else can see.
Local-first also means honest state. ReDock maps every status light in its UI from real process state, and the MCP surface reports the same truth. When a tool call says the site is running, the process tree is actually alive. Agents can’t be lied to any more than you can.
What driving it looks like
You open Claude Desktop and type: “Spin up a WordPress site for the bakery client, add an about page and a contact page, and give me a login link.”
The agent calls list_sites, sees nothing matching, creates the site, waits for it to report running, then writes both pages using the site’s registered block patterns. It finishes by requesting a magic login link — single-use, expiring, generated fresh — so you land in wp-admin without typing a password. The whole exchange is a conversation on your side and a series of verifiable tool calls on the agent’s side. We cover the login mechanism in detail in WordPress magic login: how agents get into wp-admin without passwords.
Content quality depends on the authoring layer, not just the model. ReDock’s tools are patterns-first: agents compose pages from the theme’s real block patterns instead of hallucinating markup. That’s the subject of Gutenberg MCP: how an AI writes real block content and AI edits your WordPress site: patterns-first authoring explained.
Which clients work
Any MCP client can connect. In practice that means:
- Claude Desktop — conversational site building and content work
- Claude Code — agentic coding sessions that also control the sites they’re coding against
- Cursor — same idea from inside your editor
- Anything else that speaks MCP — the endpoint is plain
localhost:47200
No plugin to install inside WordPress, no API keys to mint per site. One endpoint sees every site ReDock hosts. Setup is a few lines of client config; the MCP docs walk through each client.
You don’t even need a cloud model. ReDock includes a built-in agent and a local-LLM catalog sized to your Mac’s RAM, so tool calls can come from a model that never sends a byte off the machine — see No API key AI: run a local model that can actually do things.
FAQ
Do I need to install anything inside WordPress?
No. ReDock provisions and hosts the sites itself, so the MCP surface is part of the platform, not a plugin you add per site. Sites created through ReDock are agent-operable from the first boot.
Is this safe to point an agent at?
Safer than most alternatives. Sites are local, capabilities are tiered per site (design, manage, data, code), mutations carry undo hints, and there’s an activity log of what the agent changed. And magic login means no credentials are ever stored or pasted.
What does it cost?
ReDock is free. It’s a native macOS app (macOS 12+, built with Tauri and Rust — not Electron). Windows isn’t supported.
If you want an agent that can actually run WordPress instead of just talking about it, download ReDock — it takes one download and a five-minute install.