Until this month StrifeBridge MCP only worked with Claude, Cursor, and Windsurf. ChatGPT couldn’t connect at all. That’s fixed.
Why ChatGPT couldn’t connect
StrifeBridge authenticated with a bearer token: a long secret you copied from Settings and pasted into your AI client. Claude accepts that. Cursor and Windsurf accept it. ChatGPT’s connector interface does not. It expects OAuth, and if a server doesn’t offer OAuth there is no field to paste a token into.
So a large share of people who wanted to manage WordPress with AI simply had no way in. Version 3.0.0 adds full OAuth 2.1, and 3.0.1 follows it with a set of fixes worth reading about at the end of this post.
Connecting is now a click, not a copy-paste
The old flow was: open Settings, copy a URL with a secret embedded in it, paste it into your AI tool, hope you didn’t truncate it. If the secret leaked, it worked forever and there was no record of who used it.
The new flow is the one you already know from every other service. Your AI assistant sends you to your own WordPress admin. You see which application is asking and what it wants access to. You click Approve. That’s it, and no secret is ever copied by hand.
What changes underneath
The interesting part isn’t convenience.
Access is time-limited. Access tokens last an hour. Refresh tokens last thirty days and rotate every time they’re used, so a stolen one stops working as soon as the real client refreshes. Present an already-used refresh token and every token for that connection is revoked, on the assumption that something has gone wrong.
You can see and revoke connections. Settings now lists every authorized application, when it last called your site, and a Revoke button. Revocation takes effect immediately.
Requests run as a real person. This is the change with the longest tail. Previously every request executed as no user at all. Nothing was attributed, WordPress’s own permission checks had nothing to check against, and content created through the API showed up authorless in the admin, in feeds, and on author archives. An OAuth connection is bound to the administrator who approved it, so the site behaves normally and the activity log can say who did what.
The old method still works. Existing bearer token connections are untouched. The token is still in Settings, now marked as the legacy method. Use OAuth for new connections; there is no need to migrate one that already works.
Also in 3.0.1
Three fixes shipped a day after 3.0.0, one of which matters if you use custom post types.
Deletions could destroy content while reporting it recoverable. WordPress only sends built-in posts and pages to the trash. Everything else, including WooCommerce products, block-theme templates, and any custom post type, is deleted permanently. StrifeBridge passed that behaviour through and then reported the result as “trashed” based on the request rather than the outcome. Deleting a product destroyed it and told you it was recoverable.
Deletion now trashes explicitly, refuses with a clear explanation when the trash isn’t available, and reports the status the post actually ended up in. If you use custom post types, update.
The other two: an unclassified tool now defaults to the most restrictive permission level rather than a middle one, and content created through an OAuth connection is attributed to the authorizing user rather than a configured default.
A note on how this was found
The deletion bug wasn’t reported by a user. It came out of an independent audit of the codebase, the fourth so far, run specifically to look for paths where an operation could destroy something and report success. It found one, and it was fixed and released within a day.
That is the standard the plugin is being held to, because the whole proposition is running an AI assistant against a site that matters. More on that soon: the next release adds the ability to undo what an assistant did, and to require approval before it does anything destructive in the first place.
Getting started
StrifeBridge MCP is free on WordPress.org. Install it, activate it, and in Settings you’ll find both connection methods. For ChatGPT or Gemini, use the OAuth flow. For Claude, either works.
One note for self-hosted nginx: a common hardening rule blocks the OAuth discovery documents before they reach WordPress, and both will return 404. The plugin’s FAQ has the two-line fix. Apache and managed hosts are unaffected.
Download StrifeBridge MCP free from WordPress.org, or read more about what it does.