All MCP Servers
Cloud & DevOpsMCP RegistrypypiB · 71

MCP Cloudflare DNS

io.github.Ayo-Fam · Updated

Cloudflare DNS MCP server: manage zones, records, cache purge, and page rules.

At a glance

MCP Cloudflare DNS is an MCP server in the Cloud & DevOps category. It runs locally over stdio via `uvx mcp-cloudflare-dns`, and needs CF_API_TOKEN. It scores B (71/100) on the MCP Skills Hub health score as of Oct 28, 2026.

Source 0GitHub stars

One-click install

Opens your editor and pre-fills the config. Your editor will ask before adding it.

How to install MCP Cloudflare DNS in your AI client

Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.

How to install MCP Cloudflare DNS in Claude CodeAnthropic's agentic CLI

  1. Add the server

    bash
    claude mcp add mcp-cloudflare-dns -e 'CF_API_TOKEN=<CF_API_TOKEN>' -- uvx mcp-cloudflare-dns
  2. Fill in your credentials

    Replace <CF_API_TOKEN> with your real value. Keep secrets out of any config file you commit.

  3. Verify it's connected

    bash
    claude mcp list
  4. Sharing it with your team?

    Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).

  5. Use it in a session

    Ask Claude to use the tools this server exposes. It discovers them automatically.

What does MCP Cloudflare DNS need from you?

API key — Cloudflare API token with Zone DNS Edit, Zone Read, and Cache Purge permissions

  • CF_API_TOKENrequiredsecretEnvironment variable

    Cloudflare API token with Zone DNS Edit, Zone Read, and Cache Purge permissions

  • CF_ALLOW_DESTRUCTIVEoptionalEnvironment variable

    Set to 'true' to enable DNS record deletion and full cache purge

Pass secrets through your shell environment rather than committing them into a config file.

What tools does MCP Cloudflare DNS expose?

This server runs as a local package. We only query remote servers for their tool list — asking this one would mean executing it, so its tools are listed in the documentation below.

What the code can do

Source analysis currently covers npm packages only. This server ships as a Python package, which needs a different parser.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

What it can reach

  • Runs code on your machine — Executes as a local process with your user's permissions, including filesystem access.
  • Downloads at launch — The package is fetched from its registry each run unless you pin a version.
  • Last commit 4 days ago — Actively maintained.
  • 0 GitHub stars — Very little community usage so far.

Client compatibility

Claude Code: NativeClaude Desktop: NativeCursor: NativeCodex CLI: NativeWindsurf: NativeCline: NativeVS Code: Native

Health score

B · 71

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

  • Maintenance30%100%

    Last commit 4 days ago.

  • Adoption20%0%

    0 stars.

  • Transparency20%75%

    3/4: ✓ public source repo, ✓ declared license, ✓ documentation, ✗ discoverable tool list.

  • Provenance15%75%

    Links to its own repository; package linkage unverified.

  • Packaging15%100%

    Publishes a pinned version (0.1.1).

Documentation

Full README

mcp-cloudflare-dns

Cloudflare DNS MCP server for operators who need zone, record, cache, and page-rule control from an MCP client without opening the Cloudflare dashboard for every change.

Release posture: beta package, version 0.1.1 from `pyproject.toml`.

Choose your path

| You are... | Start here | Then | |---|---|---| | Installing the server in Claude/Codex/Cursor | docs/start-here.md | Quick start below | | Verifying what the server can touch | Available tools | docs/architecture.md | | Auditing packaging or release metadata | `pyproject.toml` | `server.json` |

Architecture

mermaid
flowchart TD
  U[AI operator] --> C[MCP client]
  C --> S[FastMCP server]
  E[CF_API_TOKEN] --> S
  S --> T[Tool handlers]
  T --> R[Retry wrapper]
  R --> A[Cloudflare API]
  A --> R --> T --> C

Request flow

mermaid
flowchart TD
  Q[Operator asks for a DNS change] --> H[Selected MCP tool]
  H --> I[Load token and build client]
  I --> J{Cloudflare call succeeds?}
  J -- yes --> K[Return normalized JSON result]
  J -- retryable --> L[Backoff and retry]
  L --> J
  J -- no --> M[Return error payload]

Quick start

  1. Install the package.
bash
python -m pip install mcp-cloudflare-dns
  1. Export a token with DNS permissions.
bash
export CF_API_TOKEN="your-cloudflare-api-token"

Maintain MCP Cloudflare DNS? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

markdown
[![MCP Cloudflare DNS on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/io-github-ayo-fam-mcp-cloudflare-dns)](https://mcp-skills-hub.vercel.app/mcps/io-github-ayo-fam-mcp-cloudflare-dns)

Catalog data refreshed . Something wrong? Report it.