Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Open canonical comparison link

Comparable alternatives

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence fieldCloudflare MCPMCP100 SelectedpulumiMCP100 Selected
Task fit
Best for
  • Searching and executing supported Cloudflare API operations across Workers, DNS, R2, Zero Trust, and related products
  • Investigating account configuration and operational data from an MCP client
  • Using product-specific read-oriented Cloudflare MCP endpoints for logs, analytics, and documentation
  • Infrastructure discovery and policy-aware Pulumi operations across stacks and cloud resources.
Not ideal for
  • A narrowly scoped integration when the broad Cloudflare API server is authorized with excessive permissions
  • Environments that cannot complete browser-based OAuth
  • Teams outside the publisher ecosystem or without least-privilege credentials
Avoid when
  • The agent must not be able to change DNS, security, storage, compute, or account configuration
  • You cannot inspect and restrict the OAuth permissions selected during authorization
  • Untrusted retrieved content can directly trigger execute calls without approval
  • The connected identity is broader than the task requires
  • Tool calls cannot be reviewed before consequential mutations
Provenance
Provenance details

First-party MCP

Cloudflare · Publisher source ↗

First-party MCP

ecosystem:pulumi · Publisher source ↗

Maintenance
Maintenance details

Repo: Aug 11, 2026

Package: Not documented

Repo: Not documented

Package: Not documented

Popularity evidence
GitHub stars

4,074

GitHub stars · checked 2026-08-14T18:46:26.000Z

Not documented
External adoption evidence
  • github: repository stars: 4,074Exact attributable signal.github: repository stars · Admission snapshot · checked 2026-08-14T18:46:26.000ZEvidence source ↗
Not documented
Client coverage
Client coverage details
Claude Code✓ Streamable HTTP
Claude Desktop✓ Streamable HTTP
Codex✓ Streamable HTTP
VS Code✓ Streamable HTTP
Cursor✓ Streamable HTTP
OpenCode✓ Streamable HTTP
Claude Code✓ Streamable HTTP
Claude Desktop✓ Streamable HTTP
Codex✓ Streamable HTTP
VS Code✓ Streamable HTTP
Cursor✓ Streamable HTTP
OpenCode✓ Streamable HTTP
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationCloudflare's managed remote MCP servers use Cloudflare OAuth. The current API endpoint is https://mcp.cloudflare.com/mcp and supports Streamable HTTP; the older SSE transport is deprecated.The hosted server uses Pulumi OAuth; self-hosted package use follows Pulumi access-token configuration.
CostCloudflare does not document a separate fee for connecting to its managed MCP endpoints. Charges and limits for underlying Cloudflare products, the user's Cloudflare plan, and the AI client still apply.The MCP integration has no separately verified MCP100 price conclusion. Publisher subscriptions, API usage, compute, storage, and AI-client charges may apply.
PermissionsThe Cloudflare API MCP server can search the typed Cloudflare API and execute calls across the authorized account. OAuth redirects the user to Cloudflare to select permissions. Product-specific servers expose narrower capabilities such as audit logs, DNS analytics, AI Gateway logs, GraphQL analytics, or documentation search.Pulumi organization and stack permissions govern the resources exposed; tool selection can limit the enabled surface.
Data handlingTool requests are processed by Cloudflare's hosted MCP service. For the API server, generated JavaScript runs in an isolated Dynamic Worker sandbox and can read or modify data reachable through the granted Cloudflare API permissions. Product-specific servers may return logs, prompts and responses, configuration, analytics, documents, or security findings to the MCP client.Authorized service data and tool results pass through the MCP server to the connected AI client. Review the publisher and client data policies before using sensitive cloud & devops information.
Limitations
Tradeoffs
  • The Cloudflare API server compresses more than 2,500 API endpoints into search and execute tools, reducing tool-schema context but greatly increasing potential blast radius.
  • Cloudflare also offers narrower product-specific MCP servers, which can be safer but require choosing and configuring separate endpoints.
  • The hosted service removes local runtime maintenance but sends requests and results through Cloudflare's managed MCP infrastructure.
  • Delegated infrastructure execution can create cost and production impact, so mutation tools need explicit review.
Risk contextThe two-tool search/execute design can reach a very broad API surface. Prefer a product-specific endpoint where possible, grant minimum OAuth permissions, require confirmation for execute operations, inspect audit logs, and separate untrusted content from administrative actions. This review does not claim MCP100 execution testing.Delegated infrastructure execution can create cost and production impact, so mutation tools need explicit review. Use a test environment where practical, least-privilege credentials, narrowly enabled tools, and explicit confirmation for mutations. MCP100 did not execute third-party server code during this documentation review.
Evidence date
Editorial review2026-07-242026-07-30
Candidate evidence2026-08-14T18:46:26.000Z2026-07-30T19:00:00.000Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →
Compare MCPs | MCP100 Index