10 posts in Guides.
The 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 moreA 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 morePoint 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 moreInstead 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 moreAn AI agent takes on whatever WordPress user connects it. Here is why Editor beats Administrator as that account, and how to scope the connection on purpose.
Read moreThe WordPress MCP Adapter is the official building block for AI agents. Agent Abilities for MCP adds a governed catalog, admin UI, and audit log on top of it.
Read moreCopy-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 moreHow 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 moreThe REST API and an MCP server both reach your WordPress site but solve different problems. How they differ, and why an AI agent wants the second one.
Read moreA plain explanation of the Model Context Protocol, what it means for a WordPress site, and how a governed MCP server changes what an AI agent can safely do.
Read more