Automattic WordPress MCP alternative
Replacing the Archived Automattic WordPress MCP Plugin
The Automattic wordpress-mcp repository now reads Deprecated, calls itself no longer maintained, and has been made read-only. It points readers to the MCP Adapter and the Abilities API that arrived in WordPress 6.9. If you installed it and need something kept current, WordPress MCP Connector is a free, maintained plugin with its own endpoint, OAuth sign-in for ChatGPT and Claude, and profiles.
What makes it different
- Maintained, with a current release
- Free, GPL v3
- OAuth 2.0 with PKCE
- Profiles per connection
- Reaches any plugin's Abilities
- Your server, no middleman
Cascadia vs Automattic WordPress MCP at a Glance
Three Questions That Decide It
Is the Plugin Still Maintained?
Are You Building Your Own Abilities in Code?
Does ChatGPT Need to Connect?
Side by Side
| Automattic WordPress MCP | Cascadia | |
|---|---|---|
| Maintenance | ×Deprecated and read-only (October 2026) | Current release, tested to WordPress 7.1.2 |
| Recommended path | ×README points to the MCP Adapter (October 2026) | A finished plugin, no code to write |
| Community | 945 stars and 139 forks (October 2026) | –Listed in the WordPress directory |
| Ability exposure | –Adapter abilities private until marked public (October 2026) | Off until switched on per profile |
| Transports | Adapter supports HTTP and STDIO (October 2026) | –HTTP, one JSON-RPC endpoint |
| ChatGPT sign-in | ×Not described (October 2026) | OAuth 2.0 with PKCE |
| Access limits | –Per-ability permission checks in the Adapter (October 2026) | Profiles plus the WordPress role cap |
| Setup | –Developer setup for custom abilities (October 2026) | About ten minutes from the admin screen |
Maintenance
Recommended Path
Community
Ability Exposure
Transports
ChatGPT Sign-In
Access Limits
Setup
What Ships in the Free Plugin
Both options cost nothing to install. One is archived, so the list below is what you get from a plugin that is still being released.
- A maintained MCP endpoint, now at version 2.2.0
- Core WordPress tools that need no other plugin
- Tools for menus, taxonomies, themes, plugins, and site settings
- Abilities from any plugin, listed under Access and off by default
- Profiles that narrow each connection
- OAuth 2.0 with PKCE for ChatGPT and Claude
- Application Passwords for Cursor and Windsurf
- Capability checks that follow the signed-in role
- Encrypted secrets, expiring tokens, and refresh
- Guided setup for each AI client
What a Maintained Plugin Gives You
A deprecated repository still downloads. It just stops getting fixes.
Fixes Keep Arriving
The Automattic README says the code remains for historical reference only (October 2026). Security and compatibility fixes now have to come from you. Version 2.2.0 of the Connector is tested up to WordPress 7.1.2.
Built on Current WordPress
The Abilities API moved into WordPress Core as of 6.9, per the repository notice. The Connector lists any plugin's registered Abilities and keeps each off until switched on.
ChatGPT and Claude Can Connect
ChatGPT and Claude use OAuth 2.0 with PKCE, and since 1.6.8 there is no client ID or secret to generate first.
A Way to Narrow Access
Profiles define what each connection sees, and the signed-in WordPress role caps every call.
Who Should Read This Comparison
Sites on the Archived Plugin
It works until a WordPress release changes something it relied on. Moving first is easier than moving in the middle of a live outage.
Teams Told to Use the Adapter
The Adapter is canonical and GPL-2.0-or-later, but it bridges abilities developers must register. A finished plugin saves that work.
Agencies Cleaning up Sites
A deprecated plugin on a client site can show up in audits. Replacing it with a maintained one is a quick, defensible change to explain.
Choose Automattic WordPress MCP if
- You want to study how it was built
- You are writing your own abilities in code
- You need STDIO transport through WP-CLI
Choose Cascadia if
- You still run the archived plugin on a live site
- You want ChatGPT and Claude to sign in with OAuth
- You want a maintained plugin with no code to write
How to Replace It
- 1
Note Your Current Settings
Write down which tools and which accounts your agents use today, so you can recreate the same reach on purpose.
- 2
Install the Connector and Pick a Profile
Add it from the WordPress directory, open Settings, MCP Connector, and choose a profile that matches what your agent did before, or narrower. The setup guide covers each screen.
- 3
Reconnect Your Clients
Point ChatGPT or Claude at the new address as a custom connector, or give Cursor and Windsurf a fresh Application Password.
- 4
Deactivate and Remove the Old Plugin
Once the new connection works, deactivate the archived plugin, remove it, and revoke any tokens it issued.
How Automattic WordPress MCP Stands
The Archived Repository and Its Successors
These points come from the Automattic repository and the WordPress MCP Adapter repository, read in October 2026.
Taken from Automattic wordpress-mcp repository, WordPress MCP Adapter repository. Checked October 2026.
What Clients Say About Working with Cascadia
“I’ve always dreaded website management, but Cascadia has done an incredible job with my WordPress site, making it one less thing for me to worry about.”
“I’ve worked with Cascadia for several years now. They are always ready to help in any way I ask and can implement my ideas with ease. A company that values their clients!”
“Cascadia has been great to work with! We recently needed some updates, and Cascadia was quick to get them completed! We highly recommend Cascadia Web Services.”
“Cascadia is very responsive and we’re happy with them as our primary IT vendor.”
“They do great work, been using for years. Prompt responses to requests.”
Replacing Automattic WordPress MCP?
Talk to us about your setupAsk us
Automattic WordPress MCP Alternative Questions
What the archive means for your site and how to move to a maintained plugin.
See WordPress MCP ConnectorStill have a question?
Is Automattic's wordpress-mcp still supported?
No. Its README is headed Deprecated and says it is no longer maintained. The repository banner says it is now read-only, and the code remains for historical reference only (October 2026).
What does Automattic recommend instead?
The README points readers to developer.wordpress.com/docs/mcp for current setup and names two projects, the mcp-adapter and the Abilities API (October 2026).
What is the MCP Adapter?
It is described as the official WordPress package for MCP, bridging the Abilities API to the Model Context Protocol. It supports HTTP and STDIO transports and is licensed GPL-2.0-or-later (October 2026).
Is the MCP Adapter a replacement for the Connector?
They overlap but differ. The Adapter converts abilities that a developer marks public into MCP tools. The Connector is a finished plugin with its own core tools, OAuth for ChatGPT and Claude, and profiles.
Do abilities get exposed automatically?
In the Adapter, abilities are private by default and need meta.public set to true (October 2026). In the Connector, any plugin's Abilities appear in the Access tab switched off, and you enable them per profile.
Does the Connector need WordPress 6.9?
Only for tools from other plugins, because the Abilities API arrived in 6.9. The Connector's own WordPress tools run on WordPress 5.8 or later with PHP 7.4 or later.
Can I keep the old plugin while I move?
Yes, briefly. Install the Connector, test with a narrow profile, then deactivate and remove the archived plugin. Do not leave both active longer than you need.
What happens to existing agent connections?
They stay tied to the old plugin. Reconnect each client to the new address, then remove the old plugin so any tokens it issued stop working.
How do ChatGPT and Claude connect?
Add your site address as a custom connector and sign in to WordPress. Since version 1.6.8 there is no client ID or secret to create first.
How do Cursor and Windsurf connect?
They use a WordPress Application Password and the config the Client Setup tab generates. Application Passwords only work on a site served over HTTPS.
Where does the archived plugin still win?
On community size and as a reference. Its repository has 945 stars and 139 forks (October 2026), and it shows how an early MCP plugin for WordPress was structured, which is what its README says the code is kept for. For a live site that needs fixes, it no longer helps.
Is the Connector free?
Yes. It is GPL v3 in the WordPress directory, with no paid tier, no trial, and no license key. It works on any number of sites.
Does my data leave my server?
No. The MCP client calls the REST API on your own site. We run no relay, and nothing is sent to us.
Can you handle the move for us?
Yes. We can install the Connector, pick profiles for each connection, reconnect your clients, and remove the old plugin. That is a managed service or a one-off job, and it is optional.
When should I use the MCP Adapter instead?
When your developers are building custom abilities and tools of their own and want a library to expose them. For connecting an agent today without writing code, a finished plugin is quicker.
