WP Webhooks alternative
The WP Webhooks Alternative, Run For You
What makes it different
The short version
The short case for Cascadia over WP Webhooks
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
- Zero External Dependencies
- ChatGPT via OAuth 2.0
- Claude via OAuth 2.0
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
- Claude via OAuth 2.0
- Cursor and Windsurf Support
- Guided Client Setup
What our team takes on
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.
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.
Works with any plugin’s Abilities
It covers WordPress core itself, and any plugin that registers WordPress Abilities gets tools here too, each switched off until you turn it on.
One endpoint, every client
One JSON-RPC 2.0 endpoint on your own domain serves every client. ChatGPT and Claude authorize over OAuth 2.0 with your site address alone, while Cursor, Windsurf and other editors connect with a WordPress Application Password.
Who this comparison is for
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.
Stores with big catalogs
The connector reaches your store through the abilities WooCommerce registers, each one switched on by you. Ask for the change, check what came back, and keep the audit trail your user account already produces.
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
Start narrow. A read-only profile shows you exactly what the agent can see before you give it permission to change anything, and you can widen access once the results earn your trust.
- 3
Connect your AI client
3.
- 4
Put it to work
Ask for what you want in plain language. 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.