What 1.7.2 adds: a consent screen that shows who is asking
The sign-in screen now identifies a connector by its verified redirect host rather than the name it sends, and the Activity Log records every MCP request that reaches WordPress.
Read moreThe governed agent blog
Plain guides, governance notes, and honest use cases for running an AI agent against your own WordPress site.
What we fixed in the 1.7.2 connection release
A default of ours stopped ChatGPT connecting. Also fixed: a mangled redirect address, a session ID handed back for a session that was never written, and a tool list that could exhaust memory.
Read moreYour agent signs in, then nothing happens
A completed sign-in with no ability calls after it means the request never reached WordPress. How to read that signal in the Activity Log, confirm it at the CDN, and fix it.
Read moreA read-only look at your site and its plugins
Point an agent at a WordPress site for a plain inventory of the basics and the installed plugins, without handing it any power to change a thing.
Read moreOne search across every post type
Instead of hunting post type by post type, ask an agent once and see everywhere a phrase, product name, old link, or claim appears across your whole site.
Read moreThe abilities we deliberately left out
Most of the pitch is about what you can switch on. This post is about the floor under all of it: what an agent cannot do here, no matter what you enable.
Read moreWhat we fixed in the 1.7.1 correctness release
A fix-only release: WPML sweeps now read every configured language, tool discovery matches permission, and a broken discovery route resolves again.
Read moreWhat 1.7.0 adds: Enable all writes, and a fuller audit log
Version 1.7.0 adds a one-click way to enable a section's ordinary writes, deliberately leaving deletes and high-risk abilities locked, plus a fuller audit log.
Read moreWhat we fixed in the 1.7.0 correctness release
Version 1.7.0 closes an OAuth revocation race, stops a payment gateway credential leak, and fixes four ACF writes that were destroying content.
Read more