Skip to content
Cloudflare Code Mode MCP

Cloudflare Code Mode MCP

by Cloudflare
Released
1 views
Apache-2.0
Repository Docs
Featured Cloud & Infrastructure

Summary

The whole Cloudflare API — 2,500+ endpoints — behind two tools. The agent writes JavaScript instead of picking from a tool list, cutting the context cost by about 99.9%.

Features

  • search() — query the Cloudflare OpenAPI spec from JavaScript to find the right operation
  • execute() — run authenticated Cloudflare API calls from JavaScript
  • Covers 2,500+ endpoints across DNS, Workers, R2, D1, KV, Zero Trust and the rest
  • ~1,000 tokens of tool definitions instead of ~1.17M — a ~99.9% reduction
  • Context footprint stays fixed however large the API grows
  • Pagination, branching and multi-call chaining inside a single execution
  • Remote OAuth server, MCP 2026-07-28 stateless Streamable HTTP

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it.
  3. Restart the agent — the "Cloudflare Code Mode MCP" tools will be available.
{
  "mcpServers": {
    "cloudflare-code-mode-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.cloudflare.com/mcp"
      ]
    }
  }
}

Description

Code Mode is Cloudflare's answer to a problem every large API hits when it meets MCP: exposing 2,500+ endpoints as individual tools would cost roughly 1.17 million input tokens of tool definitions, which no context window can absorb. Cloudflare's server exposes two tools instead, and the definitions come to about 1,000 tokens — a ~99.9% reduction that stays fixed no matter how many endpoints the API grows to.

The two tools are search() and execute(), and both take JavaScript. search() queries the OpenAPI specification so the agent can find the right operation and its shape; execute() runs authenticated Cloudflare API calls. Because the agent is writing code rather than emitting one tool call at a time, it can paginate, branch on a response and chain several operations inside a single execution, then return only the data it actually needs. Cloudflare's framing is that "the code acts as a compact plan" — the multi-step work happens server-side instead of as a dozen round trips through the model's context.

This covers the entire Cloudflare surface: DNS, Workers, R2, D1, KV, Durable Objects, Zero Trust, Cache, Images, Stream — anything the REST API reaches. That breadth is also the caution: an agent with execute() can change account configuration, so scope the OAuth grant and the agent's remit accordingly. For a narrower blast radius, Cloudflare's per-product MCP servers expose one domain each.

The server is remote and OAuth-authenticated at https://mcp.cloudflare.com/mcp, supports the MCP 2026-07-28 stateless specification, and was announced on 20 February 2026.

Related MCP Servers

MCP: SigNoz MCP Server

by SigNoz

New

Query SigNoz metrics, traces, logs, alerts and dashboards in natural language — and create alerts, dashboards and saved views back, with deep links into the UI.

Cloud & Infrastructure
2 views

MCP: Vanta

by Vanta

Featured

Vanta's official remote MCP server — query controls, tests, vendors, vulnerabilities and policies across SOC 2 and ISO 27001, and remediate failing tests from your agent.

ProductivityCloud & Infrastructure
4 views
Browse all MCP servers →