Zapier alternative
What You Get Instead Of Running Zapier Yourself
What makes it different
The short version
Where a managed service beats running Zapier alone
Permission checks inherit the WordPress role you authenticated as. It is free and GPL licensed, and nothing you do passes through our servers.
What you get here
- Zero External Dependencies
- ChatGPT via OAuth 2.0
- Claude via OAuth 2.0
- Cursor and Windsurf Support
- Guided Client Setup
- OAuth 2.0 with PKCE
- Encrypted Client Secrets
- Token Expiry and Refresh
What ships in the standard plan here
Everything in this list ships as standard.
- Zero External Dependencies
- ChatGPT via OAuth 2.0
- Claude via OAuth 2.0
- Cursor and Windsurf Support
- Guided Client Setup
- OAuth 2.0 with PKCE
- Encrypted Client Secrets
- Token Expiry and Refresh
- Capability Checks on Every Call
- Admin-Only Authorization
Where we go further
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
Compare that with a static token sitting in a config file forever. An access token here lasts an hour and a refresh token thirty days, and you can revoke the whole connection from WordPress without rotating anything else.
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
Requests travel from your MCP client to your own REST API and back. No relay service sits in the middle.
Who this comparison is for
Stores with big catalogs
The connector reaches your store through the abilities WooCommerce registers, each one switched on by you, so what an agent can change there is whatever WooCommerce offers.
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
Describing the problem to an assistant that can actually look at your site beats hunting for a tutorial written for an older version.
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
For ChatGPT or Claude, paste your site address into the assistant and sign in. For Cursor, Windsurf or another editor, create a WordPress Application Password and copy the generated config from the Client Setup tab.
- 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.