Make alternative
The Managed Way To Replace Make
What makes it different
The short version
What you get here instead of Make
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
- 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
What ships in the standard plan here
Everything in this list ships as standard.
- 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
- WordPress Abilities From Any Plugin
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.
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.
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
Every connection gets a profile, and the profile decides which tools are exposed. Start read-only and an assistant can research your archive without changing a thing.
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
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
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.