What can @cloudflare/mcp-server-cloudflare do?

cloudflare api resource enumeration and discovery, zone and domain management via mcp tool interface, dns record crud operations with schema validation, cloudflare workers deployment and management, kv namespace and key-value store operations, firewall rule and waf policy configuration, ssl/tls certificate and domain validation management, analytics and log data retrieval with filtering, page rules and url routing configuration, rate limiting and ddos protection rule management

@cloudflare/mcp-server-cloudflare

MCP ServerFree

MCP server for interacting with Cloudflare API

Open Source

/ 100

10 capabilities

Capabilities10 decomposed

cloudflare api resource enumeration and discovery

Medium confidence

Exposes Cloudflare API endpoints as MCP tools through a schema-based registry that maps REST API operations to callable functions. The server introspects Cloudflare's API surface and generates tool definitions dynamically, allowing clients to discover available resources (zones, DNS records, workers, etc.) without hardcoding endpoint knowledge. Uses MCP's tool protocol to advertise capabilities and handle parameter validation against Cloudflare's API schemas.

Solves for

Discover what Cloudflare resources and operations are available programmaticallyUnderstand the required parameters and response formats for Cloudflare API callsIntegrate Cloudflare management into LLM agent workflows without manual API documentation lookup

Best for

AI agents and LLM applications that need to manage Cloudflare infrastructure

Developers building multi-tool orchestration systems where Cloudflare is one capability

Teams automating Cloudflare operations through natural language interfaces

Requires

Cloudflare API token or API key with appropriate permissions

Node.js 16+ runtime

MCP client implementation that supports tool calling protocol

Limitations

Discovery is limited to operations exposed by Cloudflare's public API — internal or beta endpoints may not be available

Schema generation depends on Cloudflare maintaining accurate API documentation — breaking changes in Cloudflare's API require server updates

No caching of schema definitions — each client connection may trigger re-enumeration overhead

What makes it unique

Implements MCP server pattern specifically for Cloudflare's REST API surface, translating Cloudflare's native API schemas into MCP's tool calling protocol with automatic parameter validation and response marshaling

vs alternatives

Provides native Cloudflare integration through MCP standard (vs custom REST wrappers), enabling seamless composition with other MCP servers in multi-tool agent architectures

zone and domain management via mcp tool interface

Medium confidence

Wraps Cloudflare's zone management APIs (create, list, update, delete zones) as callable MCP tools. Handles authentication via Cloudflare API tokens, constructs properly-formatted HTTP requests to Cloudflare's endpoints, and parses responses into structured data. Supports filtering, pagination, and bulk operations on zones through parameterized tool calls that abstract away HTTP details.

Solves for

Create or delete DNS zones in Cloudflare programmaticallyList and filter zones by account or statusUpdate zone settings (nameservers, plan level, etc.) through natural language commands

Best for

Infrastructure automation agents managing multi-tenant DNS

Developers building Cloudflare management dashboards with LLM interfaces

DevOps teams automating zone provisioning in CI/CD pipelines

Requires

Cloudflare API token with zone management permissions

Valid Cloudflare account

MCP client capable of invoking parameterized tools

Limitations

Requires Cloudflare API token with zone:edit permissions — cannot operate with read-only tokens

Zone creation/deletion operations are asynchronous in Cloudflare but MCP tool responses are synchronous — no built-in polling for operation completion

Bulk zone operations are not atomic — partial failures in multi-zone requests may leave inconsistent state

What makes it unique

Exposes Cloudflare zone operations through MCP's stateless tool protocol, allowing LLM agents to perform DNS infrastructure changes without managing HTTP sessions or authentication state directly

vs alternatives

Simpler than building custom REST clients for Cloudflare zone APIs — MCP abstraction handles auth, error handling, and response parsing automatically

dns record crud operations with schema validation

Medium confidence

Provides MCP tools for creating, reading, updating, and deleting DNS records within Cloudflare zones. Validates record types (A, AAAA, CNAME, MX, TXT, etc.) and required fields against Cloudflare's DNS record schema before submission. Handles TTL configuration, proxying settings (orange/gray cloud), and batch record operations through parameterized tool calls that map to Cloudflare's DNS API endpoints.

Solves for

Add or modify DNS records (A, CNAME, MX, TXT) for a domainConfigure DNS routing and failover policiesBulk import or update DNS records from structured data

Best for

Agents automating DNS configuration for multi-domain deployments

Developers building DNS management interfaces with natural language control

Infrastructure teams managing DNS records across many zones

Requires

Cloudflare API token with dns_records:edit permission

Valid zone ID in Cloudflare account

MCP client supporting parameterized tool invocation

Limitations

Record type validation is limited to Cloudflare's supported types — custom record types or DNSSEC operations may not be available

TTL minimum is 60 seconds (or 1 second for Enterprise) — cannot set arbitrary low TTLs

Batch operations lack transactional guarantees — partial failures leave some records modified and others unchanged

What makes it unique

Implements client-side schema validation for DNS records before API submission, catching invalid record types or missing required fields before round-tripping to Cloudflare, reducing latency and API errors

vs alternatives

More robust than raw REST clients because it validates DNS record schemas locally and provides structured error messages for invalid configurations

cloudflare workers deployment and management

Medium confidence

Exposes Cloudflare Workers APIs as MCP tools for deploying, updating, listing, and deleting serverless functions. Handles script upload (JavaScript/WebAssembly), environment variable binding, route configuration, and KV namespace attachment through parameterized tool calls. Abstracts the Workers API's multipart form encoding and script deployment workflow into simple tool invocations.

Solves for

Deploy or update a Cloudflare Worker script from codeConfigure routes and bindings for WorkersList deployed Workers and their metadataDelete or disable Workers

Best for

Developers building serverless deployment automation with LLM agents

Teams managing multiple Worker scripts across environments

Infrastructure platforms that need to provision edge functions programmatically

Requires

Cloudflare API token with workers_scripts:edit permission

Valid Cloudflare account with Workers enabled

JavaScript or WebAssembly code to deploy

Limitations

Script upload is limited to Cloudflare's size limits (1MB for free tier, 10MB for paid) — large scripts must be split or use bundling

Environment variables and secrets are stored in Cloudflare's system — no local secret management integration

Workers deployment is asynchronous but MCP tools return synchronously — no built-in polling for deployment completion

What makes it unique

Wraps Cloudflare Workers' multipart form-based deployment API in MCP tool protocol, allowing LLM agents to deploy edge functions without understanding HTTP multipart encoding or Workers-specific deployment mechanics

vs alternatives

Simpler than wrangler CLI for programmatic deployments because it integrates directly into MCP agent workflows without subprocess management or CLI parsing

kv namespace and key-value store operations

Medium confidence

Provides MCP tools for reading, writing, listing, and deleting key-value pairs in Cloudflare KV namespaces. Supports metadata operations (expiration, custom metadata), bulk operations, and namespace management through parameterized tool calls. Handles KV's eventual consistency model and provides structured responses for key enumeration and value retrieval.

Solves for

Store and retrieve configuration or session data in Cloudflare KVBulk import or export key-value dataManage KV namespace lifecycle (create, delete, list namespaces)Set expiration policies on KV keys

Best for

Agents managing distributed configuration or cache data

Developers building stateful serverless applications with KV backends

Teams automating data migration or backup to Cloudflare KV

Requires

Cloudflare API token with kv:edit permission

Valid KV namespace ID

MCP client supporting parameterized tool invocation

Limitations

KV has eventual consistency — reads immediately after writes may return stale data

Key size is limited to 512 bytes and value size to 512MB — very large values require chunking

Bulk operations (list, delete) are paginated — large namespaces require multiple tool calls

What makes it unique

Abstracts Cloudflare KV's REST API (including pagination and eventual consistency semantics) into simple MCP tool calls, allowing agents to use KV as a distributed state store without managing HTTP details or consistency concerns

vs alternatives

More accessible than raw KV API clients because MCP tools handle pagination, error handling, and response parsing automatically

firewall rule and waf policy configuration

Medium confidence

Exposes Cloudflare's firewall and Web Application Firewall (WAF) APIs as MCP tools for creating, updating, listing, and deleting firewall rules. Supports rule expressions (IP-based, country-based, user-agent matching), actions (block, challenge, allow), and priority ordering. Handles rule validation and conflict detection through parameterized tool calls that map to Cloudflare's rules engine.

Solves for

Create firewall rules to block or challenge traffic based on IP, country, or request propertiesUpdate or delete existing firewall rulesList active firewall rules and their priority orderConfigure WAF managed rulesets and sensitivity levels

Best for

Security teams automating threat response through agents

Developers building dynamic firewall management interfaces

Infrastructure platforms that need to enforce security policies programmatically

Requires

Cloudflare API token with firewall:edit permission

Valid zone ID

Understanding of Cloudflare's rule expression syntax

Limitations

Rule expressions are limited to Cloudflare's expression language — complex custom logic may not be expressible

Rule priority is global per zone — many rules can cause performance degradation

WAF managed rulesets are updated by Cloudflare — custom rule modifications may be overwritten on updates

What makes it unique

Provides MCP interface to Cloudflare's rules engine, allowing agents to compose firewall rules using natural language that is translated to Cloudflare expression syntax, with validation before deployment

vs alternatives

More accessible than raw firewall APIs because it abstracts rule expression syntax and provides structured validation feedback

ssl/tls certificate and domain validation management

Medium confidence

Exposes Cloudflare's SSL/TLS certificate APIs as MCP tools for managing certificates, domain validation, and HTTPS settings. Supports operations like requesting certificates, checking validation status, configuring minimum TLS versions, and managing custom certificates. Handles Cloudflare's certificate provisioning workflow and validation challenges through parameterized tool calls.

Solves for

Request or renew SSL/TLS certificates for domainsCheck certificate validation status and expirationConfigure minimum TLS version and cipher suitesUpload custom certificates to Cloudflare

Best for

Agents automating certificate lifecycle management

Developers building HTTPS compliance monitoring

Teams managing SSL/TLS configuration across many domains

Requires

Cloudflare API token with ssl:edit permission

Valid zone ID

Domain pointing to Cloudflare nameservers (for automatic provisioning)

Limitations

Cloudflare's automatic certificate provisioning is limited to Cloudflare-managed nameservers — external DNS requires manual validation

Custom certificate uploads require PEM-formatted certificates and private keys — no format conversion

Certificate renewal is automatic for Cloudflare-managed domains but requires manual renewal for custom certificates

What makes it unique

Wraps Cloudflare's certificate provisioning and validation workflow in MCP tools, allowing agents to manage HTTPS without understanding certificate formats, validation challenges, or renewal mechanics

vs alternatives

Simpler than managing certificates through Cloudflare's dashboard or raw API because MCP tools abstract certificate lifecycle and validation status tracking

analytics and log data retrieval with filtering

Medium confidence

Provides MCP tools for querying Cloudflare's analytics APIs to retrieve traffic data, request logs, and performance metrics. Supports filtering by time range, country, status code, and other dimensions. Returns structured analytics data (requests, bandwidth, cache hit ratio, etc.) through parameterized tool calls that map to Cloudflare's GraphQL or REST analytics endpoints.

Solves for

Retrieve traffic analytics for a zone over a time periodQuery request logs filtered by status code, country, or other criteriaGet performance metrics (cache hit ratio, response times, etc.)Export analytics data for reporting or analysis

Best for

Agents analyzing traffic patterns and generating reports

Developers building analytics dashboards with natural language queries

Teams investigating security incidents or performance issues

Requires

Cloudflare API token with analytics:read permission

Valid zone ID

Time range within data retention window

Limitations

Analytics data is delayed by up to 30 minutes — real-time monitoring is not available

Historical data retention varies by plan (free: 3 days, pro: 30 days, business: 90 days, enterprise: 1 year)

Detailed request logs are limited to Enterprise plans — lower tiers have aggregated analytics only

What makes it unique

Abstracts Cloudflare's analytics APIs (both GraphQL and REST) into unified MCP tools with automatic time range validation and data retention checking, preventing queries for unavailable historical data

vs alternatives

More user-friendly than raw analytics APIs because it handles time zone conversion, data aggregation, and retention limits automatically

page rules and url routing configuration

Medium confidence

Exposes Cloudflare's Page Rules API as MCP tools for creating, updating, listing, and deleting page rules that apply settings to specific URL patterns. Supports actions like caching, forwarding, security settings, and performance tuning through parameterized tool calls. Handles rule priority and pattern matching through Cloudflare's URL pattern syntax.

Solves for

Create page rules to apply caching or security settings to URL patternsConfigure URL forwarding or redirectsSet performance or security settings for specific pathsList and manage existing page rules

Best for

Developers automating URL-based configuration management

Teams managing complex routing and caching policies

Agents configuring Cloudflare settings based on URL patterns

Requires

Cloudflare API token with page_rules:edit permission

Valid zone ID

Understanding of Cloudflare's URL pattern syntax

Limitations

Page Rules are being phased out in favor of Cloudflare Rules — new features are added to Rules, not Page Rules

Maximum number of page rules varies by plan (free: 3, pro: 20, business: 125, enterprise: unlimited)

URL pattern matching is limited to Cloudflare's glob syntax — complex regex patterns are not supported

What makes it unique

Provides MCP interface to Cloudflare's Page Rules with automatic pattern validation and priority conflict detection, preventing invalid or conflicting rules from being deployed

vs alternatives

More accessible than raw Page Rules API because it validates URL patterns and provides structured error messages for invalid configurations

rate limiting and ddos protection rule management

Medium confidence

Exposes Cloudflare's rate limiting and DDoS protection APIs as MCP tools for creating and managing rate limit rules and DDoS mitigation policies. Supports threshold configuration, action selection (block, challenge, log), and request counting methods. Handles rule validation and conflict detection through parameterized tool calls that map to Cloudflare's rate limiting endpoints.

Solves for

Create rate limiting rules to prevent abuse or DDoS attacksConfigure DDoS sensitivity and mitigation thresholdsList and update existing rate limit rulesMonitor rate limit violations and blocked requests

Best for

Security teams automating DDoS response

Developers building abuse prevention into applications

Infrastructure platforms protecting against rate-based attacks

Requires

Cloudflare API token with rate_limit:edit permission

Valid zone ID

Understanding of rate limiting thresholds and actions

Limitations

Rate limiting rules are evaluated in order — rule ordering affects performance and accuracy

Threshold configuration is limited to requests per minute — sub-minute or per-second limits are not available

DDoS protection is automatic but sensitivity levels are coarse-grained — fine-tuning requires custom rules

What makes it unique

Wraps Cloudflare's rate limiting APIs in MCP tools with automatic threshold validation and conflict detection, preventing misconfigured rules from blocking legitimate traffic

vs alternatives

More accessible than raw rate limiting APIs because it abstracts threshold configuration and provides structured feedback on rule effectiveness

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Related Artifactssharing capabilities

Artifacts that share capabilities with @cloudflare/mcp-server-cloudflare, ranked by overlap. Discovered automatically through the match graph.

MCP Server46

Cloudflare MCP Server

Manage Cloudflare Workers, KV, R2, and DNS via MCP.

dns record management and zone configuration via mcpmcp-compliant tool exposure via http streaming transportdns analytics and traffic pattern analysis via mcp

3 shared capabilities

MCP Server31

@cloudflare/mcp-server-cloudflare

MCP server for interacting with Cloudflare API

dns analytics and query pattern analysismulti-server tool registry with schema-based function calling

2 shared capabilities

MCP Server25

dns

Infrastructure as Code for MCP domains / DNS management

multi-domain dns record management with service-specific routing

1 shared capability

MCP Server21

Mailgun

** - Interact with Mailgun API.

domain configuration and dns record management

1 shared capability

MCP Server22

Hostinger

** - Official [Hostinger API](https://developers.hostinger.com/) MCP server for services managment.

dns record management and nameserver configuration

1 shared capability

MCP Server46

mcp-for-beginners

This open-source curriculum introduces the fundamentals of Model Context Protocol (MCP) through real-world, cross-language examples in .NET, Java, TypeScript, JavaScript, Rust and Python. Designed for developers, it focuses on practical techniques for building modular, scalable, and secure AI workfl

mcp resource and tool schema definition with validation

1 shared capability

Best For

✓AI agents and LLM applications that need to manage Cloudflare infrastructure
✓Developers building multi-tool orchestration systems where Cloudflare is one capability
✓Teams automating Cloudflare operations through natural language interfaces
✓Infrastructure automation agents managing multi-tenant DNS
✓Developers building Cloudflare management dashboards with LLM interfaces
✓DevOps teams automating zone provisioning in CI/CD pipelines
✓Agents automating DNS configuration for multi-domain deployments
✓Developers building DNS management interfaces with natural language control

Known Limitations

⚠Discovery is limited to operations exposed by Cloudflare's public API — internal or beta endpoints may not be available
⚠Schema generation depends on Cloudflare maintaining accurate API documentation — breaking changes in Cloudflare's API require server updates
⚠No caching of schema definitions — each client connection may trigger re-enumeration overhead
⚠Requires Cloudflare API token with zone:edit permissions — cannot operate with read-only tokens
⚠Zone creation/deletion operations are asynchronous in Cloudflare but MCP tool responses are synchronous — no built-in polling for operation completion
⚠Bulk zone operations are not atomic — partial failures in multi-zone requests may leave inconsistent state

Requirements

Cloudflare API token or API key with appropriate permissionsNode.js 16+ runtimeMCP client implementation that supports tool calling protocolCloudflare API token with zone management permissionsValid Cloudflare accountMCP client capable of invoking parameterized toolsCloudflare API token with dns_records:edit permissionValid zone ID in Cloudflare account

Input / Output

Accepts: MCP tool discovery requests, Tool invocation with JSON parameters matching Cloudflare API schemas, Zone name (string), Account ID (string), Zone configuration parameters (JSON object with plan, nameservers, etc.), Record type (enum: A, AAAA, CNAME, MX, TXT, SRV, etc.), Record name/subdomain (string), Record content/value (string or IP address), TTL (integer, seconds), Proxied flag (boolean for Cloudflare proxying), Script code (JavaScript string or WebAssembly binary), Script name (string), Routes (array of route patterns), Environment variables (key-value object), KV namespace bindings (array of binding configurations), Namespace ID (string), Key (string, max 512 bytes), Value (string or binary, max 512MB), Expiration time (Unix timestamp, optional), Custom metadata (JSON object, optional), Rule expression (Cloudflare expression language string), Action (enum: block, challenge, allow, log, etc.), Priority (integer), Description (string, optional), Enabled flag (boolean), Domain name (string), Certificate type (enum: universal, dedicated, custom), Custom certificate (PEM-formatted string, optional), Private key (PEM-formatted string, optional), Minimum TLS version (enum: 1.0, 1.1, 1.2, 1.3), Zone ID (string), Time range (start and end Unix timestamps), Metrics (array of metric names: requests, bandwidth, cache_hit_ratio, etc.), Filters (object with country, status_code, content_type, etc.), Granularity (enum: 1m, 5m, 1h, 1d), URL pattern (string with wildcards), Actions (array of action objects with setting and value), Request matcher (path, IP, country, etc.), Threshold (requests per minute), Action (enum: block, challenge, log), Duration (seconds to apply action)

Produces: MCP tool definitions (name, description, input schema), Cloudflare API responses (JSON-structured resource data), Zone object (ID, name, status, nameservers, plan), List of zones with metadata, Operation status/confirmation, DNS record object (ID, type, name, content, TTL, status), List of records in zone, Confirmation of create/update/delete operation, Worker deployment confirmation (script ID, URL, status), List of deployed Workers with metadata, Deployment error details, Key-value pair (key, value, metadata), List of keys (with pagination cursor), Operation confirmation (put, delete, list), Rule object (ID, expression, action, priority, status), List of rules in zone, Validation errors for invalid expressions, Certificate object (domain, issuer, expiration, status), Validation status (pending, validated, failed), TLS configuration (minimum version, ciphers), Analytics data (time series with metric values), Aggregated statistics (total requests, bandwidth, cache ratio), Request logs (individual request details for Enterprise), Page rule object (ID, pattern, actions, priority, status), List of page rules in zone, Validation errors for invalid patterns, Rate limit rule object (ID, matcher, threshold, action, status), List of rate limit rules, Violation statistics (blocked requests, top offenders)

UnfragileRank

Adoption39%(30% weight)

Quality20%(25% weight)

Ecosystem30%(25% weight)

Match Graph10%(15% weight)

Freshness75%(5% weight)

UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.

Type: MCP Server

10 capabilities

Visit @cloudflare/mcp-server-cloudflare→

Package Details

npm

Registry

0.2.0

Version

4,720

Weekly Downloads

About

MCP server for interacting with Cloudflare API

Alternatives to @cloudflare/mcp-server-cloudflare

IntelliCode50Extension

AI-assisted development

Compare →

GitHub Copilot Chat53Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot52Extension

Your AI pair programmer

Compare →

Claude Code for VS Code52Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

Are you the builder of @cloudflare/mcp-server-cloudflare?

Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.

Claim this artifact →Verification via email

Get the weekly brief

New tools, rising stars, and what's actually worth your time. No spam.

Data Sources

mcp registry

Looking for something else?

Search →

Capabilities10 decomposed

cloudflare api resource enumeration and discovery

Medium confidence

Solves for

Best for

AI agents and LLM applications that need to manage Cloudflare infrastructure

Developers building multi-tool orchestration systems where Cloudflare is one capability

Teams automating Cloudflare operations through natural language interfaces

Requires

Cloudflare API token or API key with appropriate permissions

Node.js 16+ runtime

MCP client implementation that supports tool calling protocol

Limitations

Discovery is limited to operations exposed by Cloudflare's public API — internal or beta endpoints may not be available

Schema generation depends on Cloudflare maintaining accurate API documentation — breaking changes in Cloudflare's API require server updates

No caching of schema definitions — each client connection may trigger re-enumeration overhead

What makes it unique

vs alternatives

Provides native Cloudflare integration through MCP standard (vs custom REST wrappers), enabling seamless composition with other MCP servers in multi-tool agent architectures

zone and domain management via mcp tool interface

Medium confidence

Solves for

Create or delete DNS zones in Cloudflare programmaticallyList and filter zones by account or statusUpdate zone settings (nameservers, plan level, etc.) through natural language commands

Best for

Infrastructure automation agents managing multi-tenant DNS

Developers building Cloudflare management dashboards with LLM interfaces

DevOps teams automating zone provisioning in CI/CD pipelines

Requires

Cloudflare API token with zone management permissions

Valid Cloudflare account

MCP client capable of invoking parameterized tools

Limitations

Requires Cloudflare API token with zone:edit permissions — cannot operate with read-only tokens

Zone creation/deletion operations are asynchronous in Cloudflare but MCP tool responses are synchronous — no built-in polling for operation completion

Bulk zone operations are not atomic — partial failures in multi-zone requests may leave inconsistent state

What makes it unique

Exposes Cloudflare zone operations through MCP's stateless tool protocol, allowing LLM agents to perform DNS infrastructure changes without managing HTTP sessions or authentication state directly

vs alternatives

Simpler than building custom REST clients for Cloudflare zone APIs — MCP abstraction handles auth, error handling, and response parsing automatically

dns record crud operations with schema validation

Medium confidence

Solves for

Add or modify DNS records (A, CNAME, MX, TXT) for a domainConfigure DNS routing and failover policiesBulk import or update DNS records from structured data

Best for

Agents automating DNS configuration for multi-domain deployments

Developers building DNS management interfaces with natural language control

Infrastructure teams managing DNS records across many zones

Requires

Cloudflare API token with dns_records:edit permission

Valid zone ID in Cloudflare account

MCP client supporting parameterized tool invocation

Limitations

Record type validation is limited to Cloudflare's supported types — custom record types or DNSSEC operations may not be available

TTL minimum is 60 seconds (or 1 second for Enterprise) — cannot set arbitrary low TTLs

Batch operations lack transactional guarantees — partial failures leave some records modified and others unchanged

What makes it unique

vs alternatives

More robust than raw REST clients because it validates DNS record schemas locally and provides structured error messages for invalid configurations

cloudflare workers deployment and management

Medium confidence

Solves for

Deploy or update a Cloudflare Worker script from codeConfigure routes and bindings for WorkersList deployed Workers and their metadataDelete or disable Workers

Best for

Developers building serverless deployment automation with LLM agents

Teams managing multiple Worker scripts across environments

Infrastructure platforms that need to provision edge functions programmatically

Requires

Cloudflare API token with workers_scripts:edit permission

Valid Cloudflare account with Workers enabled

JavaScript or WebAssembly code to deploy

Limitations

Script upload is limited to Cloudflare's size limits (1MB for free tier, 10MB for paid) — large scripts must be split or use bundling

Environment variables and secrets are stored in Cloudflare's system — no local secret management integration

Workers deployment is asynchronous but MCP tools return synchronously — no built-in polling for deployment completion

What makes it unique

vs alternatives

Simpler than wrangler CLI for programmatic deployments because it integrates directly into MCP agent workflows without subprocess management or CLI parsing

kv namespace and key-value store operations

Medium confidence

Solves for

Store and retrieve configuration or session data in Cloudflare KVBulk import or export key-value dataManage KV namespace lifecycle (create, delete, list namespaces)Set expiration policies on KV keys

Best for

Agents managing distributed configuration or cache data

Developers building stateful serverless applications with KV backends

Teams automating data migration or backup to Cloudflare KV

Requires

Cloudflare API token with kv:edit permission

Valid KV namespace ID

MCP client supporting parameterized tool invocation

Limitations

KV has eventual consistency — reads immediately after writes may return stale data

Key size is limited to 512 bytes and value size to 512MB — very large values require chunking

Bulk operations (list, delete) are paginated — large namespaces require multiple tool calls

What makes it unique

vs alternatives

More accessible than raw KV API clients because MCP tools handle pagination, error handling, and response parsing automatically

firewall rule and waf policy configuration

Medium confidence

Solves for

Best for

Security teams automating threat response through agents

Developers building dynamic firewall management interfaces

Infrastructure platforms that need to enforce security policies programmatically

Requires

Cloudflare API token with firewall:edit permission

Valid zone ID

Understanding of Cloudflare's rule expression syntax

Limitations

Rule expressions are limited to Cloudflare's expression language — complex custom logic may not be expressible

Rule priority is global per zone — many rules can cause performance degradation

WAF managed rulesets are updated by Cloudflare — custom rule modifications may be overwritten on updates

What makes it unique

vs alternatives

More accessible than raw firewall APIs because it abstracts rule expression syntax and provides structured validation feedback

ssl/tls certificate and domain validation management

Medium confidence

Solves for

Request or renew SSL/TLS certificates for domainsCheck certificate validation status and expirationConfigure minimum TLS version and cipher suitesUpload custom certificates to Cloudflare

Best for

Agents automating certificate lifecycle management

Developers building HTTPS compliance monitoring

Teams managing SSL/TLS configuration across many domains

Requires

Cloudflare API token with ssl:edit permission

Valid zone ID

Domain pointing to Cloudflare nameservers (for automatic provisioning)

Limitations

Cloudflare's automatic certificate provisioning is limited to Cloudflare-managed nameservers — external DNS requires manual validation

Custom certificate uploads require PEM-formatted certificates and private keys — no format conversion

Certificate renewal is automatic for Cloudflare-managed domains but requires manual renewal for custom certificates

What makes it unique

vs alternatives

Simpler than managing certificates through Cloudflare's dashboard or raw API because MCP tools abstract certificate lifecycle and validation status tracking

analytics and log data retrieval with filtering

Medium confidence

Solves for

Best for

Agents analyzing traffic patterns and generating reports

Developers building analytics dashboards with natural language queries

Teams investigating security incidents or performance issues

Requires

Cloudflare API token with analytics:read permission

Valid zone ID

Time range within data retention window

Limitations

Analytics data is delayed by up to 30 minutes — real-time monitoring is not available

Historical data retention varies by plan (free: 3 days, pro: 30 days, business: 90 days, enterprise: 1 year)

Detailed request logs are limited to Enterprise plans — lower tiers have aggregated analytics only

What makes it unique

vs alternatives

More user-friendly than raw analytics APIs because it handles time zone conversion, data aggregation, and retention limits automatically

page rules and url routing configuration

Medium confidence

Solves for

Create page rules to apply caching or security settings to URL patternsConfigure URL forwarding or redirectsSet performance or security settings for specific pathsList and manage existing page rules

Best for

Developers automating URL-based configuration management

Teams managing complex routing and caching policies

Agents configuring Cloudflare settings based on URL patterns

Requires

Cloudflare API token with page_rules:edit permission

Valid zone ID

Understanding of Cloudflare's URL pattern syntax

Limitations

Page Rules are being phased out in favor of Cloudflare Rules — new features are added to Rules, not Page Rules

Maximum number of page rules varies by plan (free: 3, pro: 20, business: 125, enterprise: unlimited)

URL pattern matching is limited to Cloudflare's glob syntax — complex regex patterns are not supported

What makes it unique

Provides MCP interface to Cloudflare's Page Rules with automatic pattern validation and priority conflict detection, preventing invalid or conflicting rules from being deployed

vs alternatives

More accessible than raw Page Rules API because it validates URL patterns and provides structured error messages for invalid configurations

rate limiting and ddos protection rule management

Medium confidence

Solves for

Best for

Security teams automating DDoS response

Developers building abuse prevention into applications

Infrastructure platforms protecting against rate-based attacks

Requires

Cloudflare API token with rate_limit:edit permission

Valid zone ID

Understanding of rate limiting thresholds and actions

Limitations

Rate limiting rules are evaluated in order — rule ordering affects performance and accuracy

Threshold configuration is limited to requests per minute — sub-minute or per-second limits are not available

DDoS protection is automatic but sensitivity levels are coarse-grained — fine-tuning requires custom rules

What makes it unique

Wraps Cloudflare's rate limiting APIs in MCP tools with automatic threshold validation and conflict detection, preventing misconfigured rules from blocking legitimate traffic

vs alternatives

More accessible than raw rate limiting APIs because it abstracts threshold configuration and provides structured feedback on rule effectiveness

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Alternatives to @cloudflare/mcp-server-cloudflare

IntelliCode50Extension

AI-assisted development

Compare →

GitHub Copilot Chat53Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot52Extension

Your AI pair programmer

Compare →

Claude Code for VS Code52Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

@cloudflare/mcp-server-cloudflare

Capabilities10 decomposed

cloudflare api resource enumeration and discovery

zone and domain management via mcp tool interface

dns record crud operations with schema validation

cloudflare workers deployment and management

kv namespace and key-value store operations

firewall rule and waf policy configuration

ssl/tls certificate and domain validation management

analytics and log data retrieval with filtering

page rules and url routing configuration

rate limiting and ddos protection rule management

Related Artifactssharing capabilities

Cloudflare MCP Server

@cloudflare/mcp-server-cloudflare

dns

Mailgun

Hostinger

mcp-for-beginners

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

Package Details

About

Categories

Alternatives to @cloudflare/mcp-server-cloudflare

Are you the builder of @cloudflare/mcp-server-cloudflare?

Get the weekly brief

Data Sources

@cloudflare/mcp-server-cloudflare

Capabilities10 decomposed

cloudflare api resource enumeration and discovery

zone and domain management via mcp tool interface

dns record crud operations with schema validation

cloudflare workers deployment and management

kv namespace and key-value store operations

firewall rule and waf policy configuration

ssl/tls certificate and domain validation management

analytics and log data retrieval with filtering

page rules and url routing configuration

rate limiting and ddos protection rule management

Related Artifactssharing capabilities

Cloudflare MCP Server

@cloudflare/mcp-server-cloudflare

dns

Mailgun

Hostinger

mcp-for-beginners

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

Package Details

About

Categories

Alternatives to @cloudflare/mcp-server-cloudflare

Are you the builder of @cloudflare/mcp-server-cloudflare?

Get the weekly brief

Data Sources