MCP Server
Cloudflare MCP Servers
Suite of domain-specific MCP servers providing curated, typed tools for Cloudflare products including Workers, observability, DNS analytics, and browser automation
What is Cloudflare MCP Servers?
Cloudflare maintains a collection of remote MCP servers that expose purpose-built tools across their platform ecosystem, deployed as individual services under the mcp.cloudflare.com domain. This repository contains 14 distinct servers including Documentation (docs.mcp.cloudflare.com/mcp), Workers Bindings (bindings.mcp.cloudflare.com/mcp), Observability (observability.mcp.cloudflare.com/mcp), and Browser Rendering (browser.mcp.cloudflare.com/mcp), each optimized for specific product areas. All servers support both streamable-http transport on /mcp endpoints and the deprecated SSE transport on /sse paths. Unlike Cloudflare's Code Mode server in the cloudflare/mcp repository which provides broad API coverage through code execution, these domain-specific servers offer guided, typed interactions tailored to workflows like debugging Workers logs, managing storage bindings, querying analytics via GraphQL, or capturing web page screenshots. Authentication requires Cloudflare API tokens with appropriate scopes, configured via HTTP headers when using remote connections through mcp-remote or native MCP client support.
Key capabilities
Multi-Transport Support with Streamable HTTP and SSE
Each server exposes both streamable-http transport via /mcp endpoints and legacy SSE transport via /sse paths, allowing clients to choose between the modern JSON-RPC over HTTP approach or server-sent events based on compatibility requirements.
Domain-Specific Server Architecture for Product Areas
Provides 14 specialized servers like Workers Bindings for storage and AI primitives, Observability for logs and analytics, Browser Run for web scraping and screenshots, and DNS Analytics for performance optimization, each with curated tools for its domain.
Remote MCP Deployment with Per-Server URLs
All servers are deployed as remote endpoints under *.mcp.cloudflare.com subdomains, accessed via npx mcp-remote <URL> or direct configuration in MCP clients that support first-class remote servers like Cloudflare AI Playground.
Cloudflare API Token Authentication via HTTP Headers
Authentication uses Cloudflare API tokens passed through HTTP headers in client configuration, with each server requiring specific permission scopes based on the Cloudflare products it accesses (e.g., Workers API for Bindings server, Logs API for Observability).
Use cases
Debugging Workers with Log Analysis and Metrics
The Observability server (observability.mcp.cloudflare.com/mcp) enables AI assistants to query Workers logs, analyze error patterns, inspect tail logs in real-time, and retrieve analytics data to diagnose production issues without manual dashboard navigation.
Building Workers Applications with Storage Bindings
The Workers Bindings server (bindings.mcp.cloudflare.com/mcp) exposes tools for interacting with KV, R2, D1, Vectorize, and AI bindings, allowing AI assistants to scaffold storage integrations and test data operations during development workflows.
Web Content Extraction with Browser Rendering
The Browser Run server (browser.mcp.cloudflare.com/mcp) provides tools to fetch web pages, convert HTML to markdown, and capture screenshots, enabling AI assistants to analyze web content, verify deployments, or extract data from external sites.
Infrastructure Analytics via GraphQL Queries
The GraphQL server (graphql.mcp.cloudflare.com/mcp) allows AI tools to construct and execute Cloudflare GraphQL analytics queries, aggregating metrics across zones, Workers, and security products for reporting and anomaly detection.
MCP capabilities
Tools
Search Cloudflare documentation
Inspect Workers observability
Manage Workers bindings
Use browser rendering
Connection and auth
- Cloudflare API token with scopes matching the specific server's requirements
- mcp-remote package for clients without native remote MCP support
- HTTP header configuration for API token authentication
Client configuration
Claude Code
{
"type": "http",
"url": "https://observability.mcp.cloudflare.com/mcp"
}