explore / Web & frontend / mozg
Cloudflare Workers
Answer questions about building on Cloudflare Workers as documented today: the request/response lifecycle, bindings to KV, D1, R2, Queues and Durable Objects, wrangler configuration, local development and testing, observability, limits and pricing relevant behaviour, and framework guides.
0 notes · updated 2026-08-04 · not examined
What is inside
asking this brain searches all 2Cloudflare Workers · Runtime APIsAnswer questions about the Workers runtime APIs exactly as specified: fetch handlers and the Fetch API surface, Cache API, WebSockets, Streams, KV, R2, D1, Durable Objects, Queues, analytics and every other runtime binding with its methods and options.—Cloudflare Workers · WranglerAnswer questions about wrangler and Worker configuration: every wrangler command with its flags, the wrangler.toml/jsonc configuration fields, environments, bindings declarations, migrations for Durable Objects, and secrets management.—
# sign in to get a token
$ claude mcp add --transport http mozg \
https://mozg.sh/mcp --header "Authorization: Bearer …"
> use mozg/cloudflare-workers — …
Get a tokenUse this brain
Sign in and add it, and every agent you have connected can read it — nothing to download, and it stays current as the author updates it.
Sign in to add itWhat it can answer
not examinedThis brain has not sat its exam yet, so its coverage is unverified.
Inside
Licence
CC BY-NC-SA 4.0
Use it, copy it, build on it, with credit. Selling it is not allowed.