An MCP (Model Context Protocol) server that exposes the entire Cloudflare API as tools. Dynamically generates one MCP tool per API operation from the bundled Cloudflare OpenAPI spec — 2,655 operations across 1,686 endpoints covering every Cloudflare service.
MCP server exposing the entire Cloudflare API (2,655 operations) as tools — dynamic OpenAPI-driven tool generation
Estrelas
2
Ferramentas
—
Disponibilidade
—
How it works
Bundled Cloudflare OpenAPI spec (8.4 MB, 1,686 paths)
→ parse & resolve $refs (swagger-parser)
→ filter operations (optional tag/path/method filters)
→ for each operation:
→ derive tool name from operationId
→ merge path/query params + request body into a single JSON Schema
→ map HTTP method to MCP tool annotations (readOnly, destructive, idempotent)
→ register as an MCP tool with a call handler that calls the Cloudflare API
→ start MCP server over stdio
Features
Entire Cloudflare API — 2,655 operations across 436 service categories (Zones, DNS, Workers, R2, Pages, WAF, Load Balancing, Tunnels, and more)
Dynamic tool generation — tools are generated at startup from the bundled OpenAPI 3.0.3 spec
MCP tool annotations — readOnlyHint, destructiveHint, idempotentHint set automatically based on HTTP method
Tag filtering — --include-tags / --exclude-tags to expose only the API categories you need
Path filtering — --include-paths / --exclude-paths with glob patterns
Method filtering — --include-methods / --exclude-methods to restrict HTTP methods
claude mcp add --scope user --transport stdio cloudflare -- \
java -jar /path/to/cloudflare-mcp-1.0.0.jar
4. Use
> List my Cloudflare zones
> Show DNS records for example.com
> Create an A record pointing app.example.com to 1.2.3.4
> List my Workers scripts
> What firewall rules are configured on my zone?
Filtering
The full Cloudflare API has 2,655 operations. Use filters to expose only what you need:
By tag (API category)
# Only DNS and Zone tools
java -jar cloudflare-mcp.jar --include-tags "DNS Records,Zones"
# Everything except deprecated APIs
java -jar cloudflare-mcp.jar --exclude-tags "Access Bookmark applications (Deprecated)"
By path
# Only zone-related endpoints
java -jar cloudflare-mcp.jar --include-paths "/zones/**"
# Zone and DNS endpoints
java -jar cloudflare-mcp.jar --include-paths "/zones/**" --include-tags "DNS Records,Zones"
By HTTP method
# Read-only mode — only GET endpoints
java -jar cloudflare-mcp.jar --include-methods "GET"
# No deletes
java -jar cloudflare-mcp.jar --exclude-methods "DELETE"
Common filter presets
Use case
Flags
DNS management
--include-tags "DNS Records,Zones"
Workers development
--include-tags "Worker Script,Workers KV Namespace,Workers for Platforms"
stdio (one client) or http (one shared server for many clients)
stdio
--bind
Address for http
127.0.0.1
--port
Port for http
7401
--auth-token-file
File with the bearer token; required for http
Shared HTTP server
By default each Claude session starts its own copy of the server, about 450 MB each. With --transport http, one copy serves every session over MCP streamable HTTP at /mcp.
Every request must send Authorization: Bearer <token>. The server refuses to start if the token file is readable by every user, or if the token has fewer than 32 characters. Register it in Claude Code with a headersHelper that prints the header:
Every generated tool includes MCP annotations based on the HTTP method:
HTTP Method
readOnlyHint
destructiveHint
idempotentHint
GET, HEAD, OPTIONS
true
false
true
POST
false
false
false
PUT
false
false
true
PATCH
false
false
false
DELETE
false
true
true
This means Claude will treat DELETE operations with appropriate caution and won't hesitate to call GET endpoints for information gathering.
Security
Response sanitization — All API responses are wrapped in unique cryptographic boundary markers with instructions to treat the content as untrusted data. This defends against prompt injection via API responses.
Response truncation — Responses are truncated at a configurable limit (default 50k chars) to prevent context overflow.
Input validation — Required parameters are validated before API calls.
HTTP auth — In http mode, every request needs the bearer token. The compare is constant-time. Bind to 127.0.0.1 only; containers on the host network can reach loopback, and the token is what keeps them out.
Building from source
mvn clean verify
This compiles, runs all 155 tests, and produces the shaded JAR.
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Perguntas
Como instalo Cloudflare?
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Cloudflare precisa de uma chave de API?
Este registro não lista nenhuma variável de ambiente obrigatória.
Qual transporte Cloudflare usa?
Cloudflare roda localmente via stdio.
Quando Cloudflare foi verificado pela última vez?
Última verificação: 2026-10-28. MCP server exposing the entire Cloudflare API (2,655 operations) as tools — dynamic OpenAPI-driven tool generation