billflare.

Receive Workers Issues through MCP Events

Cloudflare announces signed Workers Issues notifications for compatible MCP clients, with account or single-Worker subscriptions.

Products
Workers
Source
Official docsCloudflare Changelog

Key points

  • Workers Issues groups production failures without an application SDK. New or recurring issues can trigger an agent investigation through a signed webhook event.
  • A compatible client discovers cloudflare.alert.workers_observability_real_time_issue with events/list and subscribes with events/subscribe. Scope can be an account or one Worker.
  • Setup requires Issues enabled on the Worker, the official https://mcp.cloudflare.com/mcp endpoint, Notifications Write and Workers Observability Write permissions, and a client supporting MCP Events webhooks.

Original sources

  1. Published

    Receive Workers Issues through MCP Events

    Open original source

    Cloudflare announces signed Workers Issues notifications for compatible MCP clients, with account or single-Worker subscriptions.

Author experienceWorkers +7

Lanshu: an AI-assisted Cloudflare billing risk checklist

Lanshu (@LufzzLiz) shares a six-step prompt for checking account ownership, usage, runaway consumption and budget alerts. Replies add alarm logging, email delivery checks and separate notifications.

Workers

RetainDB: a reported $36k bill from a queue loop with 81 users.

Reddit user alameenswe, building RetainDB on Workers, KV, Durable Objects and Queues, reports a Cloudflare bill of about $36k for one month with 81 users; the post body says $35,000. He attributes it to a queue consumer that re-queued async writes, 12 unbatched Durable Object writes per memory write and a kv.list() authentication fallback.

Smart Shield Argo

levelsio: disputed Smart Shield Argo charges of about $1,500/month.

Pieter Levels says around 200 sites were charged for Smart Shield Argo although he had not enabled it. He reports about $1,500 per month and later says Cloudflare refunded everything.