Opinionated Cloudflare MCP server — audit and fix your zones with a read/write security split.
pip install clawdflare AI agents are great at reading infrastructure and telling you what's wrong. They're less great at having unsupervised write access to your DNS. clawdflare splits the difference: read operations are free, write operations require a PIN via macOS popup. The agent never sees the write token.
Agents are great at reading infrastructure and telling you what's wrong. They're less great at having unsupervised write access to DNS. Clawdflare splits the difference — the read token lives in $CLOUDFLARE_API_TOKEN and the agent uses it freely; the write token is encrypted on disk and only decrypts when a human enters a PIN at a macOS popup. The agent never sees the write credential.
1. Agent audits the zone — surfaces real issues
2. Agent requests the apply — PIN popup gates the write
The agent drives every step — the read, the dry-run, the fix request, the re-audit. The one thing it cannot do is apply writes without a human at the keyboard. Perfect division of labor: agents see everything, humans authorize the things with blast radius.
pip install clawdflare
export CLOUDFLARE_API_TOKEN="your-read-only-token"
clawdflare setup-token # encrypt write token with PIN# CLI
clawdflare zones # list all zones
clawdflare audit example.com # audit against best practices
clawdflare fix example.com # dry-run: show what would change
clawdflare fix example.com --apply # apply fixes (PIN required)
clawdflare dns-records example.com # list DNS records
clawdflare ssl-status example.com # SSL/TLS summary
# MCP — add to Claude Code
clawdflare serveRead operations use CLOUDFLARE_API_TOKEN from env. Write operations decrypt a separate token with a macOS PIN popup. The agent never sees the write credentials.