Cowboy MCP vs Uncanny Automator MCP

What is Uncanny Automator's MCP server?

Uncanny Automator is a long-running WordPress automation plugin from Uncanny Owl, and since version 8.0 it includes an MCP server that lets Claude, ChatGPT and other AI apps build and run its automations and manage the site, connected through Uncanny's hosted service. The plugin has been in the WordPress.org directory since April 2020 and is at version 8.0.2 (6 November 2026), with 40,000+ active installs and a 4.9 average from 157 reviews. MCP first arrived for its own Uncanny Agent in version 7.0 (January 2026); the public "Connect your AI" server shipped in 8.0.0 on 2 November 2026.

Its strengths are real:

• Automations that keep running. The AI can build "recipes" — a trigger, conditions and actions — that then run on their own, on every form submission or order, with no AI involved and no tool use spent.
• Apps beyond WordPress. The listing (opens in new tab) claims 470+ actions across 144 plugins and apps in the free version, including services such as Mailchimp, Slack and Stripe through Uncanny's platform.
• One connection for many sites. A single sign-in covers every site on your Uncanny licence.
• No AI subscription needed. Its built-in Uncanny Agent runs on Uncanny-managed models, for people who don't use Claude or ChatGPT.
• Fine-grained switches. Every tool, integration, action and ability can be turned off, with master switches for database access, site management and file reading that an AI app cannot change.
• Older PHP. It runs on PHP 7.4.

How do Cowboy MCP and Uncanny Automator differ?

Uncanny Automator is an automation platform with an MCP server added, reached through Uncanny's relay; Cowboy MCP is an MCP server only, reached directly on your own domain, with undo behind every write.

• The connection path: AI apps connect to mcp.automatorplugin.com, which relays requests to your site and keeps a record of each request and result for 90 days. Cowboy MCP has no relay: the AI app calls /wp-json/cowboy-mcp/v1/endpoint on your domain.
• Limits: the free Lite account allows 150 tool uses a day (300 a day in the first week), shared by every site and every AI app on the account; paid plans are unlimited. Cowboy MCP has no daily cap; a rate limit of 120 requests a minute runs on your own server.
• Going back: Automator's 8.0.2 source has no undo journal or checkpoints, and a dry run only for plugin updates. Cowboy MCP journals every write for seven days, previews any write as a dry run and takes full-database checkpoints.

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

Last verified: 8 November 2026, against Uncanny Automator 8.0.2 and Cowboy MCP 1.7.7.

When is Uncanny Automator the better choice?

Uncanny Automator is the better choice when what you want from the AI is automations: describe a workflow once, and have it run on its own every time the trigger fires. A recipe built by chat keeps working after the conversation ends, costs no tool uses when it runs, and can reach apps outside WordPress through Uncanny's integrations.

It is also the better fit in these cases:

• Many sites, one sign-in. You manage several sites on one licence and want a single connection for all of them.
• No AI subscription. You want the built-in Uncanny Agent instead of bringing Claude or ChatGPT.
• Older PHP. The host runs PHP 7.4.

The tradeoffs come with the relay. Every request passes through Uncanny's service and is kept there for 90 days, the free account allows 150 tool uses a day across all your sites, and changes the AI makes cannot be undone from the plugin.

When is Cowboy MCP the better choice?

Cowboy MCP is the better choice when you want the AI to work on the site directly — editing content, running the store, updating plugins, fixing errors — with no service in between, no daily allowance and every change reversible. The AI app connects straight to your own domain, so a long task can run as many calls as it needs, and AI apps on your own machine can work on a local development site.

Every write 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, safe mode holds destructive tools on the server, and any write can be previewed as a dry run, as the security page sets out. It also goes deeper on the site itself: Gutenberg block edits, 40 WooCommerce tools, Wordfence, file writes in wp-content, real WP-CLI and database repair. The price is PHP 8.0 and no automation engine: Cowboy MCP acts when you ask, and does not schedule work of its own.

Can you run both at the same time?

Yes, and Cowboy MCP can reach Automator's recipes without a second connection. They use separate endpoints and separate sign-ins, so installing both causes no conflict. Automator also registers its recipe and site operations as WordPress abilities, marks them public and accepts calls from other MCP plugins made by an administrator. On WordPress 6.9 or newer, Cowboy MCP serves public abilities from other plugins as tools, so its agent can list, build and run Automator recipes directly, with no relay and no daily allowance. Automator's own switches still apply, and those calls appear in Cowboy MCP's audit log as not undoable, because Cowboy MCP cannot capture the state before another plugin's action. Automator's delete operation is the one exception: it brings its own confirmation step, so Cowboy MCP leaves it out.

FAQ