Cloudflare MCP Server — 84 tools for DNS, Tunnels, WAF, Zero Trust, R2, KV & Workers
{
"mcpServers": {
"io-github-itunified-io-cloudflare": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Cloudflare MCP Server — 84 tools for DNS, Tunnels, WAF, Zero Trust, R2, KV & Workers
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Commit history unknown.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
MCP Server for GCP environment for interacting with various Observability APIs.
MCP Server for kubernetes management commands
AI agents get on-chain identity, credentials, reputation, escrow, and persistent memory on XRPL.
Search, evaluate, and compare 17,000+ MCP servers — each scored on security, maintenance, and efficiency.
MCP Security Weekly
Get CVE alerts and security updates for io.github.itunified-io/cloudflare and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Slim Cloudflare MCP Server for managing DNS, zones, tunnels, WAF, Zero Trust, and security via Cloudflare API v4.
No SSH. No shell execution. API-only. 3 runtime dependencies.
75 tools across 11 domains:
npm install
cp .env.example .env # Edit with your Cloudflare API token
npm run build
node dist/index.js # stdio transport for MCP
mcp-cloudflare supports loading Cloudflare credentials from a central
HashiCorp Vault instance at startup via AppRole
authentication. This is optional — the server works fine with plain environment
variables alone.
On startup, if NAS_VAULT_ADDR is set the server performs an AppRole login,
fetches the KV v2 secret at <mount>/data/cloudflare/api, and injects the
values into the process environment before the MCP transport starts. The
loader is fully opportunistic:
NAS_VAULT_ADDR is unset, the loader is a silent no-op. No Vault
calls are made and the server behaves exactly as before.fetch (Node 20+) — no additional runtime dependencies.Explicit env vars (CLOUDFLARE_API_TOKEN etc.) > Vault > error (missing creds)
If you set CLOUDFLARE_API_TOKEN directly, the Vault loader will not
overwrite it. Vault only fills in credentials that are not already present in
the environment.
| Variable | Required | Description |
|---|---|---|
| `NA |