Cloudflare has shipped the first production use this series has seen of a feature that is not yet a specification. In Cloudflare API MCP server sends Workers Issues as MCP Events, the changelog explains that Workers Issues, Cloudflare’s built-in error monitoring that groups related production failures “without an SDK or application wrapper,” now reaches agents as MCP Events. It is “the first event it exposes.” Clients discover it with events/list and subscribe with events/subscribe, scoped to an account or a single Worker, and “when Issues detects a new or recurring issue, the server posts a signed event to the client’s webhook, so an agent can start investigating.”
There are no figures in a changelog, and the context comes from this series’ own reading. A week ago Upstash explained that MCP Events are “newer and not yet a spec,” a sketch in a working group’s incubation repository that OpenAI had shipped in ChatGPT, and that “no popular third-party MCP server emits events yet.” Cloudflare is now one. The design follows the sketch: a subscription the host refreshes, a signed delivery to a callback URL, and an agent that wakes because something happened rather than because someone asked. To use it, a developer enables Issues on a Worker and connects the API MCP server with two write permissions, Notifications and Workers Observability, from a client that supports event webhooks.
The catalog holds the surfaces this joins. The Cloudflare provider page lists 651 API pages, and the event originates on the Cloudflare Workers API side and travels through the notification system described by the Cloudflare Notification Alert Types API and the Cloudflare Notification History API. The agentic access profile now maps 5,254 operations, 2,628 of them acting and 106 human-in-the-loop, larger than when this series last read it. The event surface dimension is lit, along with the MCP server, agent skills, the agent card and dry-run mode.
The Kin Score is 80.6, exemplar band, and Agent Readiness is 72.5, agent-native. This is the fifth Cloudflare story in two weeks, and the pattern is now plain: authorization as a library, durability as a lifecycle, search as a gateway tool, skills served over MCP, and now the first push channel. The catalog measures the event surface as a described contract, and this changelog describes it with a named event type, a subscription scope and a signed delivery. Cloudflare has given agents a reason to start work without being asked. The remaining unlit dimension that matters most for that is consent identity: an agent that wakes on its own still needs a way to show who it is working for.