Developer · Local MCP server
Cloudflare MCP Pro
Cloudflare MCP: DNS, Zones, Workers, KV, R2, D1, Pages, WAF, SSL, Email, AI via REST API v4.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.helbertparanhos/cloudflare-mcp-pro- Version
- 1.1.0
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-06-22
- Updated
- 2026-06-22
- Publisher
- helbertparanhos (GitHub) · 6 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/helbertparanhos) · how
- Listed under
- Email MCP servers, Cloudflare MCP servers
- Repository
- github.com/helbertparanhos/cloudflare-mcp-pro
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | cloudflare-mcp-pro | 1.1.0 | stdio |
How to connect Cloudflare MCP Pro
Cloudflare MCP Pro runs locally from a Node.js package published to the npm registry: cloudflare-mcp-pro version 1.1.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y cloudflare-mcp-pro@1.1.0. It reads these environment variables: CLOUDFLARE_API_TOKEN (required, secret), CLOUDFLARE_ACCOUNT_ID and CLOUDFLARE_API_BASE; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"cloudflare-mcp-pro": {
"command": "npx",
"args": [
"-y",
"cloudflare-mcp-pro@1.1.0"
],
"env": {
"CLOUDFLARE_API_TOKEN": "<secret>",
"CLOUDFLARE_ACCOUNT_ID": "<value>",
"CLOUDFLARE_API_BASE": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from helbertparanhos (GitHub)
| Server | Runs |
|---|---|
| ClickUp MCP ProThe most complete ClickUp MCP server - 161 tools + clickup_raw for the full v2/v3 API. | Local · stdio |
| n8n Pro MCPManage self-hosted n8n (incl. queue mode): workflows, executions, users, audit - 51 tools. | Local · stdio |
| Post for Me MCP ProPublish, schedule and analyze social posts across 9 platforms via the Post for Me API. | Local · stdio |
| Resend Email MCPComplete Resend email MCP: full API coverage + debug layer (deliverability, DNS, bounces). | Local · stdio |
| Vercel MCP ProComplete Vercel MCP: deploys, logs, projects, env, domains, DNS, certs via the full REST API. | Local · stdio |
More developer servers
| Server | Runs |
|---|---|
| CloudcostsmcpAnchor AI FinOps to real, live cloud pricing - AWS, GCP & Azure public and enterprise rates. | Local · stdio |
| CloudeIDEDeploy from your terminal, and give an AI coding agent the same abilities over MCP. | Local · stdio |
| Cloudeval AICloud evaluations and reviews for Azure and static AWS CloudFormation (beta). Requires an account. | Local · stdio |
| CloudflareMCP server to manage Cloudflare Workers, KV, R2, Pages, DNS, and cache from your IDE. | Local · stdio |
| Cloudflare MCP ServerCloudflare MCP Server - 84 tools for DNS, Tunnels, WAF, Zero Trust, R2, KV & Workers. | Local · stdio |
| CloudforgeVisualise diagrams, generate Terraform HCL, and manage Azure/AWS/GCP infrastructure with AI. | Local · stdio |
| Cloudgate WorkflowBuild and manage Cloudgate workflow-APIs: controllers, actions, workflow graphs, and databases. | Remote · HTTPLive check: sign-in required |
| CloudoracleCloudOracle - 14-tool multi-cloud compliance MCP: AWS, Azure, GCP posture, IAM, configs. | Remote · HTTPLive check: ✓ handshake |