AI Engine alternative
The AI Engine Alternative, Run For You
What makes it different
The short version
What you get here instead of AI Engine
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
- Profile-Based Access Control
- 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
What ships in the standard plan here
Everything in this list ships as standard.
- Profile-Based Access Control
- 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
Where the service earns its keep
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.
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.
Free, with no upgrade path
Install it on as many sites as you like.
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.
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
Updating a page, fixing a form, working out why an email stopped sending. Describing the problem to an assistant that can actually look at your site beats hunting for a tutorial written for an older version.
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
Open Settings, then MCP Connector, and choose a profile. Start narrow.
- 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.