Cloudflare MCP Gateway

A centralized MCP (Model Context Protocol) gateway that aggregates multiple Cloudflare MCP services into a single unified server. Configure which services you need via environment variables and access them all through one MCP connection.

Features

• Unified Access: Single MCP server for multiple Cloudflare services
• Configurable Services: Enable only the services you need via ENABLED_SERVICES
• Dual Transport Support: Works with both stdio (Claude Desktop) and streamable HTTP (web clients)
• Tool Namespacing: Automatic prefixing prevents tool name collisions (e.g., bindings_kv_get, radar_scan)
• Graceful Degradation: Continues operating if some upstream services are unavailable

Supported Services

Installation

# Using pip
pip install cf-mcp-gateway

# Using uv
uv pip install cf-mcp-gateway

Quick Start

1. Get Cloudflare Credentials

You'll need:

• API Token: Create one at Cloudflare Dashboard
• Account ID: Found in your Cloudflare dashboard URL or account settings

2. Configure Environment

Create a .env file or set environment variables:

# Required
CLOUDFLARE_API_TOKEN=your-api-token
CLOUDFLARE_ACCOUNT_ID=your-account-id
ENABLED_SERVICES=docs,bindings,observability

# Optional
TRANSPORT=stdio  # or streamable-http
LOG_LEVEL=info

3. Run the Gateway

# Using the CLI
cf-mcp-gateway

# Or as a Python module
python -m cf_mcp_gateway

Usage with MCP Clients

Claude Desktop

Add to your Claude Desktop configuration (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

{
  "mcpServers": {
    "cloudflare": {
      "command": "python",
      "args": ["-m", "cf_mcp_gateway"],
      "env": {
        "CLOUDFLARE_API_TOKEN": "your-api-token",
        "CLOUDFLARE_ACCOUNT_ID": "your-account-id",
        "ENABLED_SERVICES": "docs,bindings,observability,radar",
        "TRANSPORT": "stdio"
      }
    }
  }
}

Cursor

Add to your Cursor MCP settings:

{
  "mcpServers": {
    "cloudflare": {
      "command": "cf-mcp-gateway",
      "env": {
        "CLOUDFLARE_API_TOKEN": "your-api-token",
        "CLOUDFLARE_ACCOUNT_ID": "your-account-id",
        "ENABLED_SERVICES": "docs,bindings,observability"
      }
    }
  }
}

Streamable HTTP (Remote/Web Access)

Start the gateway with HTTP transport:

CLOUDFLARE_API_TOKEN=xxx \
CLOUDFLARE_ACCOUNT_ID=yyy \
ENABLED_SERVICES=docs,bindings,radar \
TRANSPORT=streamable-http \
GATEWAY_HOST=0.0.0.0 \
GATEWAY_PORT=3000 \
cf-mcp-gateway

The server exposes:

• POST /mcp - MCP JSON-RPC endpoint
• GET /health - Health check endpoint

Configuration Reference

Required Environment Variables

Optional Environment Variables

Tool Naming Convention

Tools from upstream services are prefixed with their service ID to avoid collisions:

• bindings_kv_get - Get value from KV
• bindings_kv_put - Put value to KV
• bindings_r2_list - List R2 objects
• radar_url_scan - Scan a URL
• docs_search - Search Cloudflare documentation

Architecture

┌─────────────────┐     ┌─────────────────────────────────┐
│   MCP Client    │────▶│   Cloudflare MCP Gateway        │
│ (Claude, etc.)  │     │                                 │
└─────────────────┘     │  ┌─────────────────────────┐    │
                        │  │   Tool Aggregator       │    │
                        │  │   - Namespacing         │    │
                        │  │   - Request routing     │    │
                        │  └─────────────────────────┘    │
                        └──────────────┬──────────────────┘
                                       │
     ┌─────────────┬─────────────┬─────┴─────┬─────────────┬─────────────┐
     ▼             ▼             ▼           ▼             ▼             ▼
┌─────────┐  ┌─────────┐  ┌─────────┐  ┌─────────┐  ┌─────────┐  ┌─────────┐
│  docs   │  │bindings │  │  radar  │  │  builds │  │ logpush │  │  ...    │
└─────────┘  └─────────┘  └─────────┘  └─────────┘  └─────────┘  └─────────┘

License

MIT License - see LICENSE file for details.