MCP authentication entered CISA's Known Exploited Vulnerabilities catalog for the first time on 2 September 2026, and the bug underneath it is the kind every engineer recognizes on sight. CVE-2026-59822 is an improper authentication flaw in BerriAI LiteLLM, the LLM proxy. The affected surface is its Model Context Protocol streamable HTTP endpoint. The mechanism is one decision made in the wrong direction: when LiteLLM key validation…

CMS agent permissions became a real operational question in the last week of July 2026, because the plumbing that makes them necessary finally stabilised. The Model Context Protocol reached its 2026-07-28 specification, and Drupal's contributed MCP Server module moved to beta the following day, joining shipped MCP servers from Strapi and Payload. The result is that a coding agent can now create, edit and publish content in production systems through a standard interface.

Agent governance is the question every CMS vendor is now answering in prose and almost none is answering in code. The claim I set out to test: no content management system meets a credible standard for agent governance, and Drupal has published the sharpest articulation of the problem in the CMS space. After reading the primary sources rather than the coverage, the first half holds comfortably.

A week ago we told you that WordPress 7.1 would arrive without the two AI capabilities everyone had attached to it, and we promised to come back on release day and mark our own homework. Here is the mark. The headline call was correct. Two supporting details were not, and one was wrong in a way that makes the story worse for WordPress, not better.

Most coverage of EmDash CMS since its April release has been speculative, because there was nothing substantial running on it in public. That changed quietly on August 12, 2026, when Cloudflare moved its own blog onto the CMS it built and then published the numbers. This piece covers what was migrated and how quickly, the stack underneath it, the performance figures Cloudflare released, the Model Context Protocol server that ships with the product, what bundled agent write access does to permission design, and what the migration does and does not demonstrate.

Google Antigravity speaks the Model Context Protocol, and in August 2026 that sentence carries almost no information. Every serious agentic harness speaks MCP. The questions worth asking about Antigravity MCP support are narrower: what happens to your context window when you connect a dozen servers, and what actually stops an agent from calling the one tool on your database server that drops a table.

Headless CMS MCP support went from novelty to table stakes in about five months, and almost nobody wrote it up as a single event. Each vendor announced its own server, each announcement was read as a product update, and the pattern underneath went uncovered. The pattern is that an entire product category agreed on how software agents talk to it, without anyone convening a standards body.

The WordPress 7.1 AI Client has been described everywhere as the release that brings streaming and embeddings to WordPress. The release lands August 19, timed to WordCamp US. If you are a plugin developer planning against those two capabilities, the schedule matters less than a detail almost nobody has checked: where the code actually is. The short version is that the AI Client is real, it has been in core since 7.0, and the two headline additions live one layer below WordPress in a standalone PHP library.