Agent Abilities for MCP ships its own copy of the official WordPress MCP Adapter. Some sites also run the Adapter as a separate plugin. Before 1.7.9, one specific combination broke. If the standalone MCP Adapter 0.7.0 was active and WordPress loaded it before this plugin, the /mcp endpoint returned a 404, so agents could not reach it. In 1.7.9 the endpoint serves in either load order.
If you do not run the standalone Adapter plugin, update as usual. If you wrote your own client or script, you may want to read the adapter changes below.
Two pieces of noise are gone
While this plugin’s copy of the Adapter was the one in use, the standalone plugin showed a red notice in wp-admin: “Another version of MCP Adapter is already loaded”. It no longer does.
The Adapter also wrote a “bundled dependency” deprecation line to the PHP error log on every request. That line no longer lands in the log, so the log is easier to read when you are looking for a real problem.
The bundled Adapter moves to 0.7.0
The copy this plugin ships moves from MCP Adapter 0.6.1 to 0.7.0. The plugin now accepts any Adapter version from 0.6.1 through 0.7.x.
Two Adapter changes in 0.7.0 are visible from outside the site. These matter most if you wrote your own client or script that talks to the endpoint directly:
- Calling a tool that does not exist now returns JSON-RPC error
-32602instead of-32003. If a script checks for the old code, update it. - After
initialize, a client must send theMCP-Protocol-Versionheader on its requests.
What did not change
No ability was added, removed or renamed. The catalog is still 179 abilities, 85 in core and 94 across the integrations, and each one keeps the same permission check. This release changes how the plugin runs next to the Adapter, not what an agent is allowed to do.
The previous release, 1.7.8, fixed bridged tools that never showed in the tool list. The full history is on the changelog.