What we fixed in the 1.6.2 hardening release
Version 1.6.2 corrects a claim about our own audit log, tightens who can edit customer data, and closes gaps in what the plugin records and sanitizes.
Read moreThe governed agent blog
Plain guides, governance notes, and honest use cases for running an AI agent against your own WordPress site.
High-risk lock and read-only mode, explained
Two controls decide what an AI agent is even offered on your WordPress site, before any per-call permission check runs: the high-risk lock and read-only mode.
Read moreWhat we fixed in the 1.4.1 standards release
A user-reported OAuth bug and six related fixes bring error responses, discovery, and tool status codes in line with what MCP and OAuth clients expect.
Read moreWhat we fixed: media reads reached past the uploader
In 1.4.3 an author-level user could read the entire WordPress media library, not just their own uploads. Here is the bug, the fix, and what else shipped.
Read moreWhat we fixed when a draft post went live
In 1.4.2 we fixed a bug where asking for a draft post published it live, two related permission gaps, and two WooCommerce order and product update bugs.
Read moreQuick Connect: one-screen setup for a WordPress MCP server
Version 1.4.0 adds a one-screen Quick Connect wizard that gets an agent connected fast, without loosening the off by default governance underneath.
Read moreFirst prompts to try on your WordPress MCP server
Copy-paste prompts for a freshly connected WordPress MCP server: safe reads, a careful draft write, and what a refusal looks like when an agent overreaches.
Read moreWPML MCP: language-aware content reads
How an AI agent reads a WPML site correctly over MCP. Content reads now take a language, report what they returned, and counts match the list scope.
Read moreAI agents for membership, subscription, and LMS stores
Let an AI agent manage customers and orders on a membership, subscription, or LMS WooCommerce store, safely and audited, now that custom roles are visible.
Read more