Cloudflare DNS MCP Server

Note: This is an unofficial MCP server and is not affiliated with or endorsed by Cloudflare.

⚠️ Security Warning

This MCP server was heavily "vibe coded" and should be used with caution. Before using:

• Review the code - This tool has access to your Cloudflare account via API token
• Clone the repository - For security, clone this repo and run a local copy rather than using npx
• Use minimal permissions - Create an API token with only the permissions you need
• Audit before use - The code is simple enough to review in ~30 minutes
• Backup DNS first - Use the backup_dns_records tool to export your DNS settings before making any modifications

git clone https://github.com/daniil-shumko/cloudflare-dns-mcp
cd cloudflare-dns-mcp && npm install && npm run build

A Model Context Protocol (MCP) server for managing Cloudflare DNS records. Use natural language with Claude Desktop or Claude Code to list domains, view DNS records, and make DNS changes.

What is MCP?

The Model Context Protocol (MCP) is an open standard that allows AI assistants like Claude to securely connect to external tools and data sources. This server implements MCP to give Claude the ability to interact with your Cloudflare DNS settings.

Features

• List and search domains - View all zones on your Cloudflare account
• Full DNS management - Create, read, update, and delete DNS records
• Backup & export - Export DNS records to JSON for backup or migration
• Multiple record types - Supports A, AAAA, CNAME, TXT, MX, NS, SRV, CAA, and PTR records
• Flexible identification - Use either zone IDs or domain names
• Cloudflare proxy support - Toggle orange cloud (proxy) status on records

Quick Start

1. Install

Option A: Install from npm (recommended)

npm install -g cloudflare-dns-mcp

Option B: Clone and build locally (for code review)

git clone https://github.com/daniil-shumko/cloudflare-dns-mcp.git
cd cloudflare-dns-mcp
npm install
npm run build

2. Create Cloudflare API Token

1. Go to Cloudflare API Tokens
2. Click "Create Token"
3. Use the "Edit zone DNS" template
4. Copy the generated token

3. Configure Claude Desktop

Add to your Claude Desktop config:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

If installed via npm (Option A):

{
  "mcpServers": {
    "cloudflare-dns": {
      "command": "npx",
      "args": ["cloudflare-dns-mcp"],
      "env": {
        "CLOUDFLARE_API_TOKEN": "your_token_here"
      }
    }
  }
}

If installed locally (Option B):

{
  "mcpServers": {
    "cloudflare-dns": {
      "command": "node",
      "args": ["/absolute/path/to/cloudflare-dns-mcp/dist/index.js"],
      "env": {
        "CLOUDFLARE_API_TOKEN": "your_token_here"
      }
    }
  }
}

4. Restart Claude Desktop

The server will now be available. Try asking Claude:

"List all my Cloudflare domains"

Available Tools

This MCP server provides 10 tools for DNS management:

| Tool | Description | |------|-------------| | add_zone | Add a new domain to your Cloudflare account | | list_zones | List all domains on your account | | get_zone_details | Get detailed info about a domain | | list_dns_records | List DNS records for a domain | | get_dns_record | Get a specific record by ID | | find_dns_records | Search records by name | | create_dns_record | Create a new DNS record | | update_dns_record | Modify an existing record | | delete_dns_record | Remove a DNS record | | backup_dns_records | Export records to JSON |

Tool Reference

add_zone

Add a new domain (zone) to your Cloudflare account. The domain's nameservers must be updated at your registrar to point to Cloudflare's nameservers after adding.

Parameters: | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | name | string | Yes | The domain name to add (e.g., example.com) | | account_id | string | Yes | Your Cloudflare account ID (found in dashboard URL or API) | | type | string | No | Zone type: full (default), partial, or secondary | | jump_start | boolean | No | Automatically fetch existing DNS records (default: false) |

Finding your Account ID:

• In Cloudflare Dashboard URL: https://dash.cloudflare.com/<ACCOUNT_ID>/...
• Via API: Use list_zones and check the account.id field in zone details

Example prompts:

• "Add example.com to my Cloudflare account"
• "Create a new zone for mydomain.io with account ID abc123"
• "Add newsite.com to Cloudflare and fetch existing DNS records"

Response includes:

• Zone ID for future operations
• Assigned nameservers to configure at your registrar
• Zone status (typically pending until nameservers are updated)

⚠️ Permission Note: This tool requires confirmation before each use and cannot be permanently auto-approved. This is a security measure as adding zones affects your Cloudflare account configuration.

list_zones

List all domains (zones) on your Cloudflare account.

Parameters: | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | page | number | No | Page number (default: 1) | | per_page | number | No | Results per page, max 50 (default: 50) | | name | string | No | Filter by domain name (partial match) | | status | string | No | Filter by status: active, pending, initializing, moved, deleted, deactivated |

Example prompts:

• "List all my domains"
• "Show me my active Cloudflare zones"
• "Find domains containing 'example'"

get_zone_details

Get detailed information about a specific domain including nameservers, plan, and settings.

Parameters: | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | zone_id | string | No* | The zone ID (32-character hex string) | | domain_name | string | No* | The domain name (e.g., example.com) |

*One of zone_id or domain_name is required.

Example prompts:

• "Show me details for example.com"
• "What nameservers is mysite.com using?"
• "What plan is example.com on?"

list_dns_records

List all DNS records for a domain.

Parameters: | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | zone_id | string | No* | The zone ID | | domain_name | string | No* | The domain name | | type | string | No | Filter by record type: A, AAAA, CNAME, TXT, MX, NS, SRV, CAA, PTR | | name | string | No | Filter by record name | | page | number | No | Page number (default: 1) | | per_page | number | No | Results per page, max 100 (default: 100) |

*One of zone_id or domain_name is required.

Example prompts:

• "What DNS records does example.com have?"
• "Show me all A records for mysite.com"
• "List the MX records for my email domain"

get_dns_record

Get details of a specific DNS record by its ID.

Parameters: | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | zone_id | string | Yes | The zone ID | | record_id | string | Yes | The DNS record ID |

find_dns_records

Search for DNS records by name. Useful for finding record IDs before updating or deleting.

Parameters: | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | zone_id | string | No* | The zone ID | | domain_name | string | No* | The domain name | | record_name | string | Yes | The record name to search for (e.g., www.example.com) | | type | string | No | Filter by record type |

*One of zone_id or domain_name is required.

Example prompts:

• "Find the record ID for www.example.com"
• "Look up the A record for api.example.com"
• "What's the record ID for mail.example.com?"

create_dns_record

Create a new DNS record.

Parameters: | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | zone_id | string | No* | The zone ID | | domain_name | string | No* | The domain name | | type | string | Yes | Record type: A, AAAA, CNAME, TXT, MX, NS, SRV, CAA | | name | string | Yes | Record name (use @ or domain for root) | | content | string | Yes | Record content (IP, hostname, or text) | | ttl | number | No | TTL in seconds, 1 = automatic (default: 1) | | proxied | boolean | No | Enable Cloudflare proxy (default: false) | | priority | number | No | Priority for MX records | | comment | string | No | Optional comment |

*One of zone_id or domain_name is required.

Example prompts:

• "Add an A record for www.example.com pointing to 192.168.1.1"
• "Create a CNAME for blog.example.com pointing to myblog.netlify.app"
• "Add a TXT record for _dmarc.example.com with value 'v=DMARC1; p=none'"
• "Set up an MX record for example.com with priority 10 pointing to mail.example.com"
• "Add an A record for api.example.com with Cloudflare proxy enabled"

update_dns_record

Update an existing DNS record. Only specify the fields you want to change.

Parameters: | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | zone_id | string | Yes | The zone ID | | record_id | string | Yes | The DNS record ID to update | | type | string | No | New record type | | name | string | No | New record name | | content | string | No | New content | | ttl | number | No | New TTL | | proxied | boolean | No | New proxy status | | comment | string | No | New comment |

Example prompts:

• "Change the IP for www.example.com to 10.0.0.1"
• "Enable Cloudflare proxy for the www record on example.com"
• "Update the TTL for api.example.com to 300 seconds"

delete_dns_record

Delete a DNS record. This action is irreversible.

Parameters: | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | zone_id | string | Yes | The zone ID | | record_id | string | Yes | The DNS record ID to delete |

Example prompts:

• "Delete the old CNAME record for legacy.example.com"
• "Remove the TXT verification record from example.com"

backup_dns_records

Backup DNS records to JSON format. Can backup a single domain or all domains on the account.

Parameters: | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | zone_id | string | No | Zone ID to backup (omit for all domains) | | domain_name | string | No | Domain to backup (omit for all domains) |

If neither parameter is provided, all domains will be backed up.

Example prompts:

• "Backup all DNS records for example.com"
• "Create a backup of all my domains' DNS records"
• "Export DNS settings for mysite.com and save to dns-backup.json"

Backup JSON format:

{
  "version": "1.0",
  "created_at": "2024-01-15T10:30:00.000Z",
  "backup_type": "single_zone",
  "zones": [
    {
      "zone_id": "abc123def456...",
      "zone_name": "example.com",
      "records": [
        {
          "type": "A",
          "name": "example.com",
          "content": "192.168.1.1",
          "ttl": 1,
          "proxied": true
        },
        {
          "type": "CNAME",
          "name": "www.example.com",
          "content": "example.com",
          "ttl": 1,
          "proxied": true
        },
        {
          "type": "MX",
          "name": "example.com",
          "content": "mail.example.com",
          "ttl": 3600,
          "proxied": false,
          "priority": 10
        }
      ],
      "record_count": 3
    }
  ],
  "total_zones": 1,
  "total_records": 3
}

Restoring from Backup

The backup format is designed to work with the create_dns_record tool. To restore:

1. Load the backup JSON file
2. For each record in each zone, use create_dns_record with the record data
3. The zone_name field identifies which domain to restore to

Example restore prompt:

"Read the backup file dns-backup.json and recreate all the DNS records for example.com"

Configuration

Claude Desktop

Config file locations:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json
• Linux: ~/.config/Claude/claude_desktop_config.json

Using npx (recommended):

{
  "mcpServers": {
    "cloudflare-dns": {
      "command": "npx",
      "args": ["cloudflare-dns-mcp"],
      "env": {
        "CLOUDFLARE_API_TOKEN": "your_token_here"
      }
    }
  }
}

Using local installation:

{
  "mcpServers": {
    "cloudflare-dns": {
      "command": "node",
      "args": ["/absolute/path/to/cloudflare-dns-mcp/dist/index.js"],
      "env": {
        "CLOUDFLARE_API_TOKEN": "your_token_here"
      }
    }
  }
}

Claude Code

Using npx (recommended):

Add to your project's .mcp.json:

{
  "mcpServers": {
    "cloudflare-dns": {
      "command": "npx",
      "args": ["cloudflare-dns-mcp"],
      "env": {
        "CLOUDFLARE_API_TOKEN": "your_token_here"
      }
    }
  }
}

Or use the CLI:

claude mcp add cloudflare-dns npx cloudflare-dns-mcp

Using local installation:

{
  "mcpServers": {
    "cloudflare-dns": {
      "command": "node",
      "args": ["/absolute/path/to/cloudflare-dns-mcp/dist/index.js"],
      "env": {
        "CLOUDFLARE_API_TOKEN": "your_token_here"
      }
    }
  }
}

Environment Variables

| Variable | Required | Description | |----------|----------|-------------| | CLOUDFLARE_API_TOKEN | Yes | Your Cloudflare API token |

Creating a Cloudflare API Token

1. Go to Cloudflare Dashboard > API Tokens
2. Click "Create Token"
3. Choose one of:
   • "Edit zone DNS" template - Pre-configured for DNS management (read/edit records)
   • Custom token with these permissions:
     • Zone.Zone → Read (required for listing and viewing zones)
     • Zone.DNS → Edit (required for DNS record management)
     • Zone.Zone → Edit (required only for add_zone tool)
4. (Optional) Restrict to specific zones for better security
5. Copy the generated token

Note: If you only need to manage DNS records for existing domains, you don't need Zone.Zone → Edit. Add this permission only if you want to use the add_zone tool to add new domains.

Development

Prerequisites

• Node.js 18 or higher
• npm or yarn

Setup

# Clone the repository
git clone https://github.com/daniil-shumko/cloudflare-dns-mcp.git
cd cloudflare-dns-mcp

# Install dependencies
npm install

# Build the project
npm run build

Available Scripts

npm run build         # Build for production
npm run dev           # Watch mode (rebuild on changes)
npm run typecheck     # Run TypeScript type checking
npm run test          # Run test suite
npm run test:watch    # Run tests in watch mode
npm run test:coverage # Run tests with coverage report
npm run start         # Run the built server

Project Structure

cloudflare-dns-mcp/
├── src/
│   ├── index.ts              # MCP server entry point
│   ├── cloudflare/
│   │   ├── client.ts         # Cloudflare API client
│   │   └── types.ts          # TypeScript type definitions
│   ├── tools/
│   │   ├── index.ts          # Tools module exports
│   │   ├── schemas.ts        # Zod validation schemas
│   │   ├── definitions.ts    # MCP tool definitions
│   │   ├── handlers.ts       # Tool implementations
│   │   └── types.ts          # Tool-specific types
│   └── utils/
│       ├── config.ts         # Configuration loader
│       └── errors.ts         # Error handling utilities
├── tests/                    # Test suite
├── dist/                     # Compiled JavaScript (generated)
├── package.json
├── tsconfig.json
└── README.md

Testing

Run the test suite:

npm test

Test the server manually:

# Set your API token
export CLOUDFLARE_API_TOKEN="your_token_here"

# Test server startup
node dist/index.js

# Test with JSON-RPC (list tools)
echo '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}' | node dist/index.js

Troubleshooting

"CLOUDFLARE_API_TOKEN environment variable is required"

The API token is not set. Make sure you've added it to your MCP configuration's env block.

"Zone not found"

• The domain might not exist in your Cloudflare account
• Your API token might not have access to this zone
• Check for typos in the domain name

"Permission denied" errors

Your API token needs both permissions:

• Zone.Zone: Read
• Zone.DNS: Edit

Server not appearing in Claude Desktop

1. Verify the path to dist/index.js is absolute (not relative)
2. Restart Claude Desktop after changing the config
3. Check that the build completed successfully (npm run build)
4. Check Claude Desktop logs for errors

Rate limiting

Cloudflare API has rate limits. If you're making many requests, you might see errors. Wait a moment and try again.

Security Best Practices

• Never commit your API token to version control
• Use environment variables for token storage
• Create minimal-permission tokens - only grant Zone.Zone:Read and Zone.DNS:Edit
• Scope tokens to specific zones if you only need to manage certain domains
• Rotate tokens periodically for better security
• Review audit logs in Cloudflare dashboard for API activity

Tool Permission Levels

This MCP server uses MCP Tool Annotations to indicate tool behavior and permission requirements:

| Tool | Read-Only | Destructive | Behavior | |------|-----------|-------------|----------| | list_zones | ✅ | - | Safe to auto-approve | | get_zone_details | ✅ | - | Safe to auto-approve | | list_dns_records | ✅ | - | Safe to auto-approve | | get_dns_record | ✅ | - | Safe to auto-approve | | find_dns_records | ✅ | - | Safe to auto-approve | | backup_dns_records | ✅ | - | Safe to auto-approve | | create_dns_record | - | - | Can be auto-approved (additive only) | | update_dns_record | - | ⚠️ | Session-only approval (can break DNS) | | delete_dns_record | - | ⚠️ | Session-only approval (irreversible) | | add_zone | - | ⚠️ | Session-only approval (account-level change) |

Tools marked with destructiveHint: true (update, delete, add_zone):

• Require confirmation before each use
• Cannot be permanently auto-approved across sessions
• Must be re-approved in new Claude Code sessions

Why these tools require extra confirmation:

• add_zone - Modifies account configuration, may have billing implications
• update_dns_record - Can misconfigure critical DNS settings (email, website)
• delete_dns_record - Irreversible action that can break services

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

1. Fork the repository
2. Create your feature branch (git checkout -b feature/amazing-feature)
3. Commit your changes (git commit -m 'Add some amazing feature')
4. Push to the branch (git push origin feature/amazing-feature)
5. Open a Pull Request

Development Guidelines

• Follow the existing code style
• Add TypeScript types for new features
• Update README for new tools or parameters
• Test changes with both Claude Desktop and Claude Code

License

This project is licensed under the MIT License - see the LICENSE file for details.

Acknowledgments

• Anthropic for Claude and the Model Context Protocol
• Cloudflare for their excellent API

Related Projects

• Model Context Protocol - The MCP specification
• MCP Servers - Official MCP server implementations
• Cloudflare API Docs - Cloudflare API documentation