Cloudflare
Give the Sazabi agent access to Workers logs and analytics, DNS, zones, bindings, builds, and Radar insights through Cloudflare's hosted MCP servers.
About
This is an MCP connector that gives the Sazabi agent tools from Cloudflare's hosted MCP servers. By default it connects to the unified account-scoped Cloudflare API server (mcp.cloudflare.com), which covers every product — Workers, DNS, zones, and more — through a single OAuth grant scoped by your account's own permissions. You can also select a narrower per-product server for Workers Observability logs and analytics, Workers Bindings (D1, R2, KV), Workers Builds, or Radar internet traffic insights.
What the agent can do:
- Reach every Cloudflare product through the unified account-scoped API server
- Query Workers Observability logs and analytics
- Inspect Workers Bindings (D1, R2, KV) and account resources
- Review Workers Builds history and status
- Browse Cloudflare Radar internet traffic insights
Prerequisites
- An active Cloudflare account
- Permission to authorize third-party OAuth applications for your Cloudflare account
Set up in the dashboard
Configure connectors in the dashboard under Settings > MCP connectors.
Open the connector
Find Cloudflare in Settings > MCP connectors.
Authorize
Start the connection; Sazabi redirects you to Cloudflare to authorize, then back. During authorization you can select which Cloudflare account to grant access to. The default server is the unified all-products API server (mcp.cloudflare.com); you can choose a narrower per-product server — Observability, Workers Bindings, Workers Builds, or Radar — from the server dropdown before connecting.
Set up with the CLI
You can also connect Cloudflare with the Sazabi CLI (installed and authenticated — see sazabi mcp-connectors reference).
Cloudflare authenticates over OAuth, so the CLI opens a browser to complete authorization:
sazabi mcp-connectors connect cloudflareAdd --read-only to restrict the connector to read-only tools, or --project-id <project> to target a specific project. In --json mode the command prints an authorization URL to open, then polls until the connection completes. Confirm the result with sazabi mcp-connectors list.
Verify
Open the connector's connection page under Settings > MCP connectors and confirm Sazabi lists the tools it discovered. Then, in a thread, ask the agent to use one of those tools and confirm it runs. If no tools appear, confirm the connection is authorized (OAuth).
Troubleshooting
No tools discovered — Disconnect and reconnect to re-authorize. Confirm the Cloudflare account you authorized has access to the products you need.
Connection shows needs attention — The authorization may have expired or been revoked; reconnect from Settings > MCP connectors.