WordPress MCP: the complete guide

What is a WordPress MCP server?

A WordPress MCP server is a plugin or service that exposes your WordPress site to AI assistants through the Model Context Protocol, an open standard for connecting AI to external tools. Once connected, an assistant like Claude or ChatGPT can act on the site — publish posts, update WooCommerce products, run backups — instead of just writing text for you to paste.

The Model Context Protocol (MCP) was introduced by Anthropic in 2024 and is now an open specification implemented by clients from many vendors. An MCP server publishes a set of tools — discrete actions like "create a post" or "update a product price" — and an MCP client, the AI app you already use, discovers those tools and calls them with your approval.

On WordPress, that server can take several forms: a plugin on a self-hosted site, a built-in feature of a hosted platform, or an adapter maintained by the WordPress project itself. This guide covers how the connection works, what an agent can actually do with it, every option available in 2026, and how to set one up safely.

How does MCP work with WordPress?

An AI assistant connects to your site as an MCP client, over a transport called Streamable HTTP — ordinary HTTPS requests to one endpoint URL. The server answers with a list of tools it offers, each described in plain language. When you ask for something, the assistant picks a tool, calls it with the details filled in, and reads the result — a loop it repeats until the job is done.

Concretely, with Cowboy MCP the flow looks like this:

1. Your AI app sends a request to a single URL on your site — https://your-site.com/wp-json/cowboy-mcp/v1/endpoint.
2. The plugin describes its 137 tools: each has a name, a plain-language description, and a defined set of inputs.
3. The assistant chooses a tool and calls it. The plugin runs the action inside WordPress — with its permission checks and safety rails — and streams the result back.

How is that different from the WordPress REST API? The REST API is the raw interface: it exposes the site's data over HTTP, but every integration has to be programmed against specific routes in advance. MCP sits one level higher — it is self-describing, so an assistant that has never seen your site can discover what's possible and act. The two are complementary rather than rivals: Cowboy MCP registers its MCP endpoint as a REST route, so MCP traffic travels over infrastructure WordPress already ships with.

What can an AI agent actually do on a WordPress site?

With Cowboy MCP, an agent gets 137 tools that cover the whole site, not just content. It can draft and schedule posts, update plugins and themes, manage users, edit WooCommerce products and orders, run Wordfence security scans, trigger backups, read error logs, and repair database tables — real administrative work, executed directly on the site rather than described to you.

Area	Tools	Examples
Core WordPress and other integrations	64	Posts, pages, media, users, plugins, themes, settings, WP-CLI, error logs, database repair, caching, Gravity Forms, Yoast SEO, UpdraftPlus backups
WooCommerce	40	Products, orders, refunds, coupons, stock, shipping zones, tax rates, sales reports
Wordfence	17	Security scans, firewall management, blocked IPs, live traffic
ACF	9	Field groups, custom fields, repeaters, options pages
Elementor	7	Templates, page builds, widget content

Each integration lights up automatically when its plugin is active — there is nothing to configure. Three real prompts, to make it concrete:

• "Turn last week's webinar notes into a blog post and schedule it for Tuesday morning."
• "Put everything in the Summer collection 20% off through Friday and email me the week's revenue."
• "Scan the site and block every IP that failed login more than ten times today."

What are your options for a WordPress MCP server?

You have five realistic options in 2026: the official WordPress mcp-adapter plugin, WordPress.com's built-in MCP server on its hosted plans, broad AI plugins such as AI Engine that include an MCP server, plugins that route MCP traffic through a hosted relay service, and self-hosted plugins that serve MCP natively from your own server. They differ mainly in where the endpoint runs and who sits between your site and your AI.

Option	What it is	Where the endpoint runs
WordPress mcp-adapter (opens in new tab) (official)	Free, vendor-neutral adapter that bridges the WordPress core Abilities API to MCP	Your server
WordPress.com built-in MCP	MCP server included with WordPress.com's paid hosted plans — available only on that platform	WordPress.com
AI Engine (Meow Apps)	Broad AI plugin — chatbots, content generation, and more — that includes an MCP server among its features	Your server
Hosted-relay plugins	Plugins that pass MCP traffic through the vendor's hosted relay service between your AI client and your site	Your server, via a third-party relay
Cowboy MCP	Native, self-hosted MCP endpoint inside a free GPL-2.0 plugin — no Node.js proxy, no relay, no external service	Your server

All of these are legitimate choices. If you want to follow the direction WordPress core itself is heading, the official adapter is the neutral pick. If your site already lives on WordPress.com, the built-in server is the shortest path. If you want a chat-assistant suite that happens to include MCP, AI Engine covers far more than site management. Cowboy MCP's focus is narrower and deeper: one self-contained endpoint, 137 tools, and a safety layer built for letting an agent loose on a live site. It is free, open source, and built in the open — the about page has the maker and press facts.

Self-hosted or hosted — which should you pick?

Pick self-hosted if you want your content and credentials to stay on your own server: the AI client talks directly to your site, and no third party sees the traffic. Pick hosted if you're already on a platform that includes MCP and would rather not manage a plugin. The tradeoff is control and privacy on one side, convenience on the other.

The privacy question is concrete, not abstract. With a hosted or relayed setup, your requests — and often your content — pass through infrastructure someone else operates, which matters if you answer to GDPR, client contracts, or your own policies. With a self-hosted endpoint, the credentials live on your server and the audit trail stays local. On the other side of the ledger, a hosted platform handles uptime, TLS, and updates for you — real work you no longer own.

Cowboy MCP sits at the self-hosted end by design: the endpoint is native to the plugin, so there is no Node.js proxy running beside WordPress, no hosted relay in the path, and no external service involved. Requests go from your AI client straight to your server, and every call is logged there.

Do you need Node.js or coding skills?

No — not for the standard path. With Cowboy MCP you install the plugin from the WordPress directory, follow the guided setup in Settings → Cowboy MCP, and connect Claude, ChatGPT, or the Codex app through a browser sign-in. There is no Node.js proxy to run, no JSON file to edit, and no code to write. A terminal path exists for developers who prefer it — and it's how Gemini connects.

The no-terminal path uses an OAuth connector: enable the Desktop Connector in the plugin settings, add your site as a custom connector in Claude, ChatGPT, or the Codex app, and approve the sign-in on your own site's consent screen (it requires a public HTTPS site).

The terminal path takes one command. Generate an API key in Settings → Cowboy MCP — it's shown once and stored only as a bcrypt hash — then register the endpoint with your tool. For Claude Code:

claude mcp add --transport http your-site https://your-site.com/wp-json/cowboy-mcp/v1/endpoint --header "Authorization: Bearer YOUR_API_KEY"

Replace your-site.com with your domain and YOUR_API_KEY with the key you generated. The same endpoint URL works in Cursor, Windsurf, Cline, Zed, VS Code, Gemini, and n8n — anything that speaks MCP over Streamable HTTP.

Is it safe to let an AI agent manage WordPress?

It can be, if the server enforces guardrails rather than trusting the model. Cowboy MCP layers six: safe mode confirms destructive actions, dry runs preview any change before it happens, an audit log records every call, a per-change undo journal reverses individual edits, database checkpoints restore the whole site, and rate limits cap a runaway agent at 120 requests per minute.

Each guardrail has a specific job:

• Safe mode — on by default; destructive tools wait for your explicit confirmation before running.
• Dry run — every write tool can report exactly what it would change without changing anything.
• Audit log — every tool call, error, and authentication event is recorded, filterable in wp-admin, and auto-pruned after 30 days.
• Undo journal — each change is captured individually, so one bad edit rolls back without touching the rest.
• Database checkpoints — one-click snapshots restore the entire site, and auto-checkpoint runs before risky operations like plugin updates.
• Rate limits and hashed keys — 120 requests per minute per key by default; keys are stored as bcrypt hashes and can be revoked individually.

Beyond those six, the most powerful operations stay behind power mode, which is off until a human administrator enables it in wp-admin, and sensitive options and dangerous database or WP-CLI commands are blocklisted outright. The security section walks through the whole model.

How do you set one up?

Three steps, about five minutes. Install a WordPress MCP plugin, generate credentials or approve a browser sign-in, and register the endpoint in your AI client. With Cowboy MCP the plugin's guided setup walks you through each client's exact flow, and the two walkthroughs below cover the most common pairings — Claude and ChatGPT — step by step.

1. Install the plugin. In wp-admin, go to Plugins → Add New, search for "Cowboy MCP", and click Install then Activate. It's free on the WordPress.org plugin directory (opens in new tab) and needs WordPress 6.2+ and PHP 8.0+.
2. Connect your AI. Open Settings → Cowboy MCP and follow the guided setup — browser sign-in for apps, API key for terminal tools. For the full walkthroughs, see how to connect WordPress to Claude or how to connect WordPress to ChatGPT.
3. Ask for something real. Start with a read-only request — "which plugins have updates pending?" — then let it act. Safe mode checks with you before anything destructive runs.

If any term in this guide is unfamiliar, the glossary defines them all in plain English.

FAQ