WordPress 7.0 shipped the platform’s first shared layer for AI, including an Abilities API that lets any feature declare what it can do, and an MCP Adapter that exposes those abilities to outside AI assistants. StrifeBridge MCP 2.2.0 plugs straight into it: every tool StrifeBridge already provides now also registers as a native WordPress ability, automatically, the moment you run it on 7.0.
What WordPress 7.0 Changed
Three pieces landed together in 7.0. The AI Client lets your server call out to models. The Abilities API gives WordPress a standard registry where a feature declares, in a structured way, exactly what it can do. The MCP Adapter exposes those registered abilities to external AI assistants over the Model Context Protocol, so a tool like Claude or Cursor can discover and call them. It is strong infrastructure, but a registry is only as useful as what gets registered in it, and a fresh 7.0 install starts almost empty: a few read-only abilities and nothing that can actually change your site.
What StrifeBridge MCP 2.2.0 Adds
StrifeBridge has always turned a WordPress site into an MCP server through its own secure endpoint. With 2.2.0, the same tools (creating and updating posts and pages, managing media, options, menus, taxonomies, widgets, users, and plugins) also register through the WordPress Abilities API. That puts dozens of working abilities into the core registry under clear categories like content, media, options, and plugins, and if you have enabled the MCP Adapter, every one of them becomes discoverable and callable by any MCP compatible client using the standard WordPress now defines. You do not configure any of it. Activate the plugin on WordPress 7.0 and the abilities are there.
Why It Integrates Seamlessly
- One source of truth. The abilities are generated from the same tool definitions StrifeBridge already uses and run through the same code path, so the two surfaces never drift apart.
- Native permissions. Because abilities run under the authenticated WordPress user, every ability is gated by a real WordPress capability. Editing content checks post editing rights, touching options requires the ability to manage options, and media operations require upload rights.
- Standards-friendly naming. Abilities follow the namespaced convention WordPress expects, so they read naturally in the registry as strifebridge/list-posts, strifebridge/update-post, and so on.
Nothing Breaks Below 7.0
The most important part of seamless is what does not change. On WordPress 7.0 and later you get the new abilities surface in addition to the existing StrifeBridge endpoint. On every supported version back to WordPress 5.6, the Abilities API simply does not exist, the new code never runs, and your setup behaves exactly as before. One plugin, no separate build, doing the right thing on both sides of the 7.0 line. If you ever want the abilities surface off, a single filter or option disables it, and your existing per-group tool toggles apply to abilities too.
Get StrifeBridge MCP
StrifeBridge MCP 2.2.0 is available now, free to start. New installs get abilities support out of the box, and existing users will see the update on the normal WordPress update screen. To see a full StrifeBridge workflow from start to finish, read How I Let Claude Fully Control My WordPress Site.
