Uncanny Automator alternative
Looking For An Uncanny Automator Alternative? We Run It Instead
What makes it different
The short version
The short case for Cascadia over Uncanny Automator
ChatGPT gets real OAuth. Every connection gets a profile, so an agent only sees the tools you allow. Permission checks inherit the WordPress role you authenticated as.
What you get here
- WordPress Abilities From Any Plugin
- MCP Server Endpoint
- WordPress Core Tools
- Profile-Based Access Control
What ships in the standard plan here
Everything in this list ships as standard.
- WordPress Abilities From Any Plugin
- MCP Server Endpoint
- WordPress Core Tools
- Profile-Based Access Control
- Zero External Dependencies
- ChatGPT via OAuth 2.0
What the managed part actually means
The other MCP options for WordPress are developer libraries or thin REST wrappers. This one is a finished WordPress connector with the awkward parts already solved.
Free, with no upgrade path
Every feature ships in the free version: every tool, OAuth for ChatGPT and Claude, profile-based access, and encrypted credential storage. It is published on WordPress.org under GPL v3, there is no paid tier, and there is no license key to buy.
Real OAuth, not a shared key
ChatGPT connects through a proper OAuth 2.0 flow with PKCE, authorized from your own login screen. Compare that with a static token sitting in a config file forever.
Profiles decide what agents see
Start read-only and an assistant can research your archive without changing a thing. Widen it later, or build a custom profile, so each client reaches exactly what it needs and nothing else.
Your server, no middleman
No relay service sits in the middle. There is no account to open with us, and nothing phones home. Your credentials and your content stay on infrastructure you already pay for.
Who this comparison is for
Agencies running many client sites
Point an agent at one site, have it audit metadata or fix a batch of redirects, then repeat on the next.
Small teams without a developer
Most WordPress jobs that feel technical are really just tedious. Updating a page, fixing a form, working out why an email stopped sending.
Content teams publishing at volume
Drafting, tagging, scheduling, and cleaning up old posts are the tasks that quietly eat editorial time.
four steps to a working connection
On a site you already administer this takes about ten minutes. Install the plugin, decide how much access to grant, then connect your client.
- 1
We assess your current setup
First we look at how things run today: what you already pay for, what is configured where, and which parts are actually causing you trouble.
- 2
Install and pick a profile
Install from the WordPress Plugin Directory and activate it. Open Settings, then MCP Connector, and choose a profile.
- 3
Connect your AI client
3.
- 4
Put it to work
The agent calls only the tools your profile allows, WordPress checks permissions on every single call, and the work lands as if you had done it by hand.