Integrations
Cloudflare
Use Cloudflare with Sazabi through native log source, manual log source, MCP connector and sandbox CLI capabilities.
Supported capabilities
MCP connectorSandbox CLINative log sourceManual log source
- MCP connector: Cloudflare — Give the Sazabi agent access to Workers logs and analytics, DNS, zones, bindings, builds, and Radar insights through Cloudflare's hosted MCP servers.
- MCP connector: Cloudflare (API token) — Give the Sazabi agent access to Cloudflare Workers, DNS, zones, and more through the hosted Cloudflare API MCP server, authenticated with an API token you mint yourself.
- Sandbox CLI: Cloudflare (cf) — Give the Sazabi agent the Cloudflare CLI (cf) in its sandbox to manage zones, DNS, and security rules.
- Sandbox CLI: Wrangler — Give the Sazabi agent the Wrangler CLI (wrangler) in its sandbox to deploy and manage Cloudflare Workers.
- Native log source: Cloudflare — Connect your Cloudflare account so Sazabi can automatically create and manage Logpush jobs for the datasets you select.
- Manual log source: Cloudflare — Create a Cloudflare Logpush job with an HTTP destination pointed at your Sazabi intake URL to stream edge network logs to Sazabi.
- Manual log source: Cloudflare Workers — Add OTLP log and trace destinations in Cloudflare Workers Observability settings and opt each Worker in via wrangler config to stream telemetry to Sazabi.
Each connection method has its own setup and permissions. Connecting one method does not enable the others.
About
Use Cloudflare with Sazabi through native log source, manual log source, MCP connector and sandbox CLI capabilities. Choose a supported capability above to see its credentials, permissions, setup instructions, and verification steps. Each method is configured separately.