ToolsMCP
Cloudflare MCP Pro
Listed in the official MCP Registry with an installable npm package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- helbertparanhos (GitHub)
- Prerequisites
- Install cloudflare-mcp-pro from npm (stdio transport). Declares 1 secret input. Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 1.1.0 · updated
- Official links
Publisher’s description
Cloudflare MCP: DNS, Zones, Workers, KV, R2, D1, Pages, WAF, SSL, Email, AI via REST API v4
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 1.1.0, registry status active. 1 package (npm)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- helbertparanhos (GitHub)
- Version observed
- 1.1.0
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.helbertparanhos%2Fcloudflare-mcp-pro/versions/1.1.0
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Inspect and manage cloud resources | Publisher description mentions “cloudflare”, “dns”. | No connection check or task run. Capability is as described by the publisher. | Rule cloud-infrastructure matched: “cloudflare”, “dns”. Rule cloud-infrastructure. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Packages
cloudflare-mcp-pro(npm, stdio, 1 secret input)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.helbertparanhos/cloudflare-mcp-pro
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.