Cowboy MCP vs Jetpack MCP

What is Jetpack's MCP feature?

Jetpack's "AI Agents & MCP" feature connects a self-hosted WordPress site to WordPress.com's own MCP server, so Claude, ChatGPT and other AI apps sign in with your WordPress.com account and reach your site through the Jetpack connection. Jetpack runs no MCP endpoint on your site: in the words of its listing (opens in new tab), "There's no MCP server to set up or host." Jetpack is Automattic's plugin, with 3,000,000+ active installs; the version checked here is 16.4 (3 November 2026), which needs WordPress 7.0 or newer.

Its strengths are real:

• Free, with nothing to host. Jetpack's MCP docs (opens in new tab) say it "works on every Jetpack-connected site, including sites on the Free plan", and WordPress.com runs the server.
• One connection for every site. A single sign-in reaches every WordPress.com and Jetpack site on your account.
• Jetpack's own services as tools. The agent can read stats, check backups, run security scans and manage the newsletter alongside posts and pages.
• Confirmation on every write. WordPress.com's tools reference (opens in new tab) says all write and delete operations go through a mandatory confirmation step, and you choose which tools may read and which may change things.
• Point-in-time restore. With paid VaultPress Backup, the whole site can be restored to an earlier moment, and the Activity Log shows which AI app made each change.

How do Cowboy MCP and Jetpack differ?

Both connect AI apps to a self-hosted WordPress site. Jetpack does it through WordPress.com's hosted server and your WordPress.com account; Cowboy MCP is the server, running on your own site, and needs no account.

• The connection path: with Jetpack, AI apps connect to public-api.wordpress.com/wpcom/v2/mcp/v1, and WordPress.com reaches your site through the Jetpack connection. With Cowboy MCP, the AI app calls /wp-json/cowboy-mcp/v1/endpoint on your domain and nothing sits in between.
• Going back: Jetpack has no per-change undo; trashed posts can be restored for 30 days, and anything else means restoring the whole site from a paid backup. Cowboy MCP journals every write for seven days, so one change can be reversed without rolling back the rest, and adds full-database checkpoints in the free plugin.
• Reach into the site: WordPress.com's tools are the same catalogue for WordPress.com and Jetpack sites — content, site editing, settings, users and plugins. Cowboy MCP adds tools that only make sense on your own server: files in wp-content, WP-CLI, database repair, error logs, and dedicated WooCommerce, Wordfence and page-builder tools.

The table lines them up; every Jetpack claim links to a primary source.

Last verified: 8 November 2026, against Jetpack 16.4, WordPress.com's MCP documentation and Cowboy MCP 1.7.7.

The architecture difference is the same one the self-hosted vs hosted WordPress MCP comparison covers: with Jetpack, WordPress.com sits in the request path and your WordPress.com account is the key; with Cowboy MCP, the only service involved is your own site.

When is Jetpack the better choice?

Jetpack is the better choice when you already use Jetpack or WordPress.com, and want one sign-in that reaches every site on your account with nothing new to install or host. The connection is free, WordPress.com keeps the server running, and every write waits for your confirmation.

It is also the better fit in these cases:

• Stats, backups and scans by chat. You want the agent to answer "which pages got the most views?" or "did last night's backup run?" from Jetpack's own services.
• A mix of WordPress.com and self-hosted sites. One connection handles both.
• Older PHP. The host runs PHP 7.4.

The tradeoffs come with the hosted path. Every request goes through WordPress.com and depends on your WordPress.com account, a mistaken edit is reversed by hand or by restoring the whole site from a paid backup, and a local development site is out of reach.

When is Cowboy MCP the better choice?

Cowboy MCP is the better choice when you want the AI app to talk to your own server and nothing else, and to undo any single change without restoring the whole site. There is no account to create and no third party between the AI app and the site, and AI apps on your own machine, such as Claude Code or Cursor, can work on a local development site.

Every write — a changed price, an edited post, an updated option — goes into the undo journal and can be rolled back on its own or in a batch for seven days by default; the undo guide walks through it. A database checkpoint is taken before plugin and theme updates, and any write can be previewed as a dry run, as the security page sets out. It reaches deeper into the site, too: Gutenberg block trees, 40 WooCommerce tools for orders, refunds and coupons, Wordfence, page builders, files, WP-CLI and database repair. The price is PHP 8.0, one connection per site, and no stats or off-site backups of its own.

Can you run both at the same time?

Yes. Jetpack's connection goes through WordPress.com and Cowboy MCP's endpoint lives on your site, so they don't touch each other, and many sites already run Jetpack. Each AI app connection is separate: an app connected to WordPress.com uses Jetpack's tools, and one connected to your site uses Cowboy MCP's. On WordPress 6.9 or newer, Cowboy MCP also serves the public abilities other plugins register, which includes Jetpack Forms' abilities for listing forms and reading or updating their responses. Calls to another plugin's abilities appear in Cowboy MCP's audit log as not undoable; each tool's own undo or restore story applies to the changes made through it.

FAQ