cloudflare-analyticslisted

# Cloudflare Analytics Cloudflare's MCP servers do **not** expose traffic analytics — the observability server covers Workers Logs only (and only when a Worker sets `[observability]` in its wrangler config), and Radar is public internet-wide data unrelated to any one account. Per-hostname numbers come from the GraphQL Analytics API, which these scripts wrap. ## Setup All scripts need `CLOUDFLARE_API_TOKEN`. Create at dash.cloudflare.com → My Profile → API Tokens → Custom token with `Zone > Analytics > Read`, `Zone > Zone > Read`, and `Account > Account Analytics > Read`. **Never let the user paste the token into the conversation** — it lands in the transcript permanently. Ask them to run the command themselves (in Claude Code, prefixed with `!`), which returns only the output. If a token does end up in the transcript, say so plainly and tell them to rotate it. ## Workflow **1. Probe limits first.** Plan entitlements decide what is answerable, and they are not derivable from the docs — the published API capability is not the same as a given zone's grant. ```bash scripts/cf-limits.sh <zone-name> ``` Returns `maxDuration` (widest single window) and `notOlderThan` (retention) per dataset. These are independent: 8-day retention with a 1-day max window means eight separate queries, not one. **2. Pick the dataset by whether you need a per-hostname breakdown.** `clientRequestHTTPHost` exists only on `httpRequestsAdaptiveGroups`, which is the most range-restricted dataset. Th