This server provides a comprehensive Model Context Protocol (MCP) interface for programmatic management of Cloudflare services through AI agents, offering 13 tools across zones, DNS, caching, Workers KV storage, and analytics.
Zone Management: List all zones with filtering by name, status, and pagination, or retrieve detailed information about specific zones including nameservers and configuration.
DNS Management: Full CRUD operations for DNS records (A, AAAA, CNAME, TXT, MX, etc.) with support for Cloudflare proxy settings, TTL configuration, and priority settings.
Workers KV Storage: Manage key-value storage with operations to list namespaces, read/write/delete key-value pairs with optional metadata and TTL expiration, and list keys with prefix filtering and pagination.
Cache Management: Purge Cloudflare cache for entire zones or selectively by specific files, cache tags, or hosts.
Analytics: Retrieve zone performance metrics including requests, bandwidth, threats, and pageviews with customizable time ranges (ISO 8601 or relative formats).
Agent-to-Agent Integration: Supports A2A protocol for seamless communication between AI agents, enabling multi-agent workflows and distributed operations through a standardized Cloudflare API interface with proper authentication and permission management.
Provides comprehensive management of Cloudflare resources including zones, DNS records, Workers KV storage, cache purging, and analytics through the Cloudflare API
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Cloudflare MCP Serverlist DNS records for example.com"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Cloudflare MCP Server
A Model Context Protocol (MCP) server that provides seamless integration with the Cloudflare API. Built with Python and managed with uv for blazing-fast dependency management.
Features
š Zone Management
List all zones in your account
Get detailed zone information
Filter zones by name and status
š§ DNS Management
List DNS records with filtering
Create new DNS records (A, AAAA, CNAME, TXT, MX, etc.)
Update existing records
Delete records
Full support for proxied records and TTL configuration
š¾ Workers KV Storage
List KV namespaces
Read values from KV
Write key-value pairs with optional TTL
Delete keys
List keys with prefix filtering
Support for metadata
ā” Cache & Performance
Purge cache (entire zone or specific files/tags/hosts)
Get zone analytics (requests, bandwidth, threats)
Installation
Prerequisites
Python 3.10 or higher
uv installed
A Cloudflare account with an API token
Quick Start with uv
Clone or create the project:
Install with uv:
Or install from the directory:
Alternative: Using pip
Configuration
Getting Your Cloudflare Credentials
API Token (Required):
Go to Cloudflare Dashboard
Click "Create Token"
Use "Edit zone DNS" template or create a custom token with the permissions you need
Copy the token
Account ID (Optional, but required for KV operations):
Go to your Cloudflare dashboard
Select any website
Scroll down on the Overview page to find your Account ID
Environment Variables
Set the following environment variables:
Or create a .env file (see .env.example).
Claude Desktop Configuration
Add to your Claude Desktop config file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Using uv (recommended):
Using Python directly:
Available Tools
The server provides 13 powerful tools for managing Cloudflare resources:
Zone Operations
list_zones- List all zones (domains) with optional filteringget_zone- Get detailed information about a specific zone
DNS Operations
list_dns_records- List DNS records with filteringcreate_dns_record- Create new DNS recordsupdate_dns_record- Update existing DNS recordsdelete_dns_record- Delete DNS records
Cache Operations
purge_cache- Purge cached content (entire zone or specific files/tags/hosts)
Workers KV Operations
list_kv_namespaces- List all KV namespacesread_kv_value- Read a value from KV storagewrite_kv_value- Write a key-value pair to KVdelete_kv_value- Delete a key from KVlist_kv_keys- List all keys in a namespace
Analytics
get_zone_analytics- Get analytics data for a zone
For detailed documentation on each tool, see EXAMPLES.md.
Agent-to-Agent (A2A) Protocol Support
This MCP server implements the Agent-to-Agent (A2A) protocol, enabling seamless communication between AI agents and autonomous systems. The A2A protocol standardizes how agents discover capabilities, authenticate, and execute operations across distributed systems.
Agent Card
The agent card is located at agent-card.json in the root directory. It provides a machine-readable description of:
Agent capabilities: Streaming support, async operations, task management
Available skills: 5 skill categories with 13 operations total
Authentication requirements: Bearer token configuration
Transport protocols: stdio-based communication via uv or Python
API schema: Complete parameter definitions for all operations
Skills for Agent-to-Agent Communication
The Cloudflare MCP Agent exposes the following skills through the A2A protocol:
1. Zone Management
Manage Cloudflare zones (domains) including listing and detailed queries.
list_zones- List all zones with filtering optionsget_zone- Retrieve detailed zone information
2. DNS Management
Comprehensive DNS record operations supporting all record types (A, AAAA, CNAME, TXT, MX, etc.).
list_dns_records- Query DNS records with filterscreate_dns_record- Create new DNS records with Cloudflare proxy supportupdate_dns_record- Modify existing DNS recordsdelete_dns_record- Remove DNS records
3. Workers KV Storage
Distributed key-value storage with metadata and TTL support.
list_kv_namespaces- List all KV namespacesread_kv_value- Retrieve values by keywrite_kv_value- Store key-value pairs with optional expirationdelete_kv_value- Delete keyslist_kv_keys- List keys with prefix filtering
4. Cache Management
Cloudflare cache purging and invalidation.
purge_cache- Purge by zone, files, tags, or hosts
5. Analytics
Zone performance metrics and analytics.
get_zone_analytics- Get requests, bandwidth, threats, and pageviews
A2A Integration Examples
Example 1: Agent-to-Agent DNS Management
An orchestrator agent can delegate DNS management to this Cloudflare agent:
Example 2: Multi-Agent Cache Invalidation
A deployment agent can coordinate with this Cloudflare agent for cache invalidation:
Example 3: KV Storage for Inter-Agent Communication
Agents can use KV storage for shared state:
A2A Authentication
When integrating with other agents, ensure the following environment variables are set:
The agent card specifies the minimum and recommended Cloudflare API permissions required for different operations.
Discovering Agent Capabilities
Other agents can discover this agent's capabilities by reading the agent-card.json file:
A2A Protocol Compliance
This agent implements the following A2A protocol features:
Structured agent card with capabilities and skills
Standardized skill and operation definitions
Type-safe parameter schemas
Authentication and authorization declarations
Transport protocol specifications (stdio)
Error handling and status reporting via MCP
For more information on the A2A protocol, see the agent card specification in agent-card.json.
Development
Using uv for Development
Project Structure
Usage Examples
Example 1: List Your Zones
Ask Claude:
"Show me all my Cloudflare zones"
Example 2: Create a DNS Record
Ask Claude:
"Create an A record for api.example.com pointing to 192.0.2.100 with proxy enabled"
Example 3: Purge Cache
Ask Claude:
"Clear the cache for https://example.com/style.css"
For more examples, see EXAMPLES.md.
API Permissions
Your Cloudflare API token needs appropriate permissions based on what operations you want to perform:
Minimum Permissions:
Zone - Zone - Read (for listing zones)
Zone - DNS - Edit (for DNS operations)
Additional Permissions for Advanced Features:
Account - Workers KV Storage - Edit (for KV operations)
Zone - Cache Purge - Purge (for cache operations)
Zone - Analytics - Read (for analytics)
Troubleshooting
Common Issues
"CLOUDFLARE_API_TOKEN environment variable is required"
Make sure you've set the environment variable
Check your Claude Desktop config has the correct token in the
envsection
"Account ID is required"
Set
CLOUDFLARE_ACCOUNT_IDenvironment variable for KV operationsOr pass
account_idparameter directly in tool calls
uv command not found
Install uv:
curl -LsSf https://astral.sh/uv/install.sh | shOr use pip as an alternative
Module not found errors
Make sure you installed the package:
uv pip install -e .Check you're in the right directory
Why uv?
This project uses uv because it's:
ā” 10-100x faster than pip
š More reliable with better dependency resolution
šÆ Simpler - one tool for everything
š Modern - built in Rust, designed for Python
Security Notes
Never commit your API token to version control
Store tokens securely using environment variables
Use API tokens instead of API keys (they're more secure and can be scoped)
Regularly rotate your API tokens
Use the minimum required permissions for your token
Contributing
Contributions are welcome! See CONTRIBUTING.md for guidelines.
License
MIT License - see LICENSE file for details.
Links
Support
For issues related to:
This MCP server: Open an issue on GitHub
Cloudflare API: Check Cloudflare Developer Docs
MCP Protocol: Check MCP Documentation
uv: Check uv Documentation