What 1.7.9 changes: it runs beside the standalone MCP Adapter plugin
With the standalone MCP Adapter 0.7.0 plugin active and loading first, the /mcp endpoint returned a 404. 1.7.9 serves in either load order and bundles adapter 0.7.0.
Read morePlain guides, governance notes, and honest use cases for running an AI agent against your own WordPress site.
With the standalone MCP Adapter 0.7.0 plugin active and loading first, the /mcp endpoint returned a 404. 1.7.9 serves in either load order and bundles adapter 0.7.0.
Read more37 bridged tools from eight plugins worked when called but never appeared in the tool list. 1.7.8 lists them, names the source namespace in bridged errors, and fixes three result bugs.
Read moreThe Abilities tab had a main Save button and four more on its cards, and pressing only the main one lost edits to exposed meta keys and content types. 1.7.7 has one button.
Read moreBefore 1.7.6, an OAuth token for the MCP endpoint also signed its holder in on other parts of a WordPress site. What it reached, what changed, and what else shipped.
Read moreWordPress hands back the same value for "there is nothing here" and "the question could not be asked". Nine review rounds on version 1.7.5 kept finding the same bug wearing a different costume, including one where a failed consent lookup read as consent granted.
Read moreThe per-connection allowlist arrived in 1.7.4 as a textarea you typed ability slugs into. In 1.7.5 it is a searchable checkbox picker with real role and client selects, so narrowing what one connection can reach no longer depends on spelling.
Read moreSend an agent to edit an Elementor page and the write used to report success while the visible page stayed exactly as it was. In 1.7.4 it refuses instead, and says which builder owns the page.
Read moreThe first release since launch that changed the ability catalog. Five new integrations, two new core abilities, a write guard for page builder pages, and an allowlist that only ever narrows.
Read moreOn sites with a persistent object cache, read-only mode and the high-risk lock could refuse to change, and the activity log recorded the change as done anyway.
Read more