Cowboy MCP vs the WordPress MCP Adapter
What is the WordPress MCP Adapter?
The WordPress MCP Adapter is the official, first-party package — maintained by the WordPress Core AI team — that converts Abilities registered through WordPress 6.9's Abilities API into Model Context Protocol primitives so AI agents can discover and run site functionality. Released under GPL-2.0-or-later, the adapter serves an MCP endpoint from your own site rather than routing traffic through anyone's cloud.
Two strengths stand out plainly. First, it is genuinely first-party: the adapter is part of the "AI Building Blocks for WordPress" initiative (opens in new tab), and it became the canonical implementation when Automattic's earlier wordpress-mcp plugin (opens in new tab) was archived in January 2026 and pointed users here — so adopting it is not a third-party trust decision. Second, it aligns with WordPress's own direction: any ability you or another plugin registers becomes callable by AI clients with no bespoke integration. The current adapter (version 0.5.0 as of writing) serves its default server over HTTP natively (opens in new tab) at /wp-json/mcp/mcp-adapter-default-server; on that server, abilities are reached through three meta-tools — discover, get-info, and execute — rather than each being listed as an individual MCP tool.
How do Cowboy MCP and the WordPress MCP Adapter differ?
How the two differ comes down to one distinction. Cowboy MCP is a finished toolset with built-in guardrails, while the WordPress MCP Adapter is core-level infrastructure that turns registered Abilities into MCP primitives for any client to call. The table below lines them up on the attributes that actually differ; every adapter claim links to its primary source.
Last verified: July 2026.
| Attribute | Cowboy MCP | WordPress MCP Adapter |
|---|---|---|
| Architecture & endpoint | Native MCP server inside WordPress at /wp-json/cowboy-mcp/v1/endpoint |
Native endpoint inside WordPress at /wp-json/mcp/mcp-adapter-default-server (repo (opens in new tab)) |
| Node.js proxy needed? | No — the endpoint is native to the plugin | Optional — the mcp-wordpress-remote proxy (opens in new tab) (Node.js 22 or newer) for stdio clients and some public HTTP setups |
| Transport | Streamable HTTP | HTTP and STDIO natively (MCP 2025-11-25); proxy adds stdio-to-HTTP (repo (opens in new tab)) |
| Authentication | API key as a hashed bearer token, or a native OAuth connector | Application password natively; JWT or OAuth 2.1 via the proxy (opens in new tab) |
| What it exposes | 137 built-in tools across content, WooCommerce, users, files, database, and diagnostics | No fixed catalog — exposes whatever Abilities are registered, reached on the default server through three meta-tools (repo (opens in new tab)) |
| Safety layer | Safe mode, dry runs, undo journal, database checkpoints, audit log | Not part of the adapter itself — confirmation, undo, and logging depend on the abilities exposed and the client (repo (opens in new tab)) |
| WooCommerce & plugin integrations | Built-in WooCommerce, Wordfence, ACF, and Elementor tools | Via any abilities others register; the proxy (opens in new tab) has an optional WooCommerce integration (consumer key and secret) |
| License & price | Free, GPL-2.0 | Free, GPL-2.0-or-later (repo (opens in new tab)) |
| Distribution | WordPress.org plugin directory (opens in new tab), with native self-updates | The WordPress/mcp-adapter package; supersedes the archived Automattic wordpress-mcp (opens in new tab) |
Both are self-hosted, native-endpoint plugins, so neither puts a relay or a vendor in your data path — the self-hosted vs hosted comparison sets out where that sits in the wider WordPress MCP plugin landscape.
When is the WordPress MCP Adapter the better choice?
The WordPress MCP Adapter is the better pick when you are building on WordPress's official AI primitives rather than shopping for a ready-made toolset. Because it is the canonical, core-team project, choosing it means there is no third-party maintainer to vet; and if your plugin or site already registers Abilities, the adapter exposes them to any AI client with no extra integration work.
That makes it a strong fit for developers defining their own agent-callable capabilities, teams standardizing on the official primitive, and anyone who expects the Abilities-plus-MCP stack to become the default WordPress path. The honest tradeoff is that the adapter gives you the pipe, not the tools: you supply or install the abilities yourself, and any confirmation, preview, or rollback behavior has to come from those abilities or your client, since the adapter does not provide a safety layer of its own.
When is Cowboy MCP the better choice?
Cowboy MCP is the better choice when you want an AI agent to manage a live site today, without authoring abilities or assembling a safety story yourself. Cowboy MCP ships 137 ready-to-use tools across content, WooCommerce, users, files, the database, and diagnostics, wrapped in a safety layer built for letting an agent act on production.
Safe mode holds destructive actions until you confirm, every write tool accepts a dry run, a per-change undo journal and one-click database checkpoints reverse mistakes, and an audit log records every call — all detailed on the security page. It also connects without a Node.js proxy: a pasted API key or a one-click OAuth connector for the Claude and ChatGPT apps, as the WordPress MCP guide walks through. Deep WooCommerce, Wordfence, ACF, and Elementor coverage comes built in, and it installs from the WordPress.org directory like any other plugin.
Can you run both at the same time?
Running Cowboy MCP and the WordPress MCP Adapter on the same site is a valid setup, not an either/or — nothing about their architecture forces a choice. Cowboy MCP and the WordPress MCP Adapter are independent GPL plugins that register separate REST endpoints (/wp-json/cowboy-mcp/v1/... and /wp-json/mcp/...), so installing both creates no conflict and no shared configuration.
In practice you might point one AI client at the adapter to exercise custom Abilities you have registered, and another at Cowboy MCP for its ready-made tools and guardrails — or run the adapter on a staging site while Cowboy MCP manages production. Because both are self-hosted native endpoints, neither adds a relay or a vendor to your data path, so running the pair keeps every request between your clients and your own server.
FAQ
Is the WordPress MCP Adapter the same as Automattic's wordpress-mcp plugin?
Not any longer. Automattic's original wordpress-mcp plugin was archived and made read-only in January 2026, and its README now tells users to migrate to the WordPress-maintained mcp-adapter, where all future work happens. If you searched for an Automattic WordPress MCP alternative or the old plugin, the WordPress MCP Adapter is its official successor. Cowboy MCP is a separate, independently maintained plugin — not a fork of either — with its own tools and safety layer.
Does the WordPress MCP Adapter need a Node.js proxy?
Not necessarily. The adapter serves its MCP endpoint over HTTP natively from WordPress, so many clients connect without any extra process. The optional mcp-wordpress-remote proxy, which needs Node.js 22 or newer, is used for stdio-only clients and some public HTTP setups that want it to handle authentication. Cowboy MCP never needs a proxy: its endpoint is native, so a browser sign-in or a pasted API key connects your client directly.
Does the adapter include the same tools as Cowboy MCP?
No — it works differently. The WordPress MCP Adapter ships no fixed catalog of tools; it exposes whatever Abilities your code, WordPress core, or other plugins register, reached on its default server through three meta-tools. Cowboy MCP ships 137 concrete tools across content, WooCommerce, security, and maintenance out of the box, plus safe mode, dry runs, undo, and an audit log. One is plumbing you build on; the other is a finished toolset.