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 fieldAISIX MCP GatewayWatchlist candidateCloudflare MCPMCP100 Selected
Task fit
Best for
  • Organizations that want one MCP gateway to aggregate upstream servers and restrict tools per caller key
  • Teams that need a policy boundary in front of multiple MCP servers
  • 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
Not ideal for
  • Small local setups that do not need a gateway layer
  • Production multi-tenant deployments before admin/operator controls are fully reviewed
  • A narrowly scoped integration when the broad Cloudflare API server is authorized with excessive permissions
  • Environments that cannot complete browser-based OAuth
Avoid when
  • Admin tokens or gateway configuration are broadly accessible
  • Caller keys are granted whole-server/all-tool access without a reason
  • 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
Provenance
Provenance details

First-party MCP

API7.ai · Publisher source ↗

First-party MCP

Cloudflare · Publisher source ↗

Maintenance
Maintenance details

Repo: Not documented

Package: Not documented

Repo: Aug 11, 2026

Package: Not documented

Popularity evidence
GitHub starsNot documented

4,074

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

Client coverage
Client coverage detailsNot documented
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
AuthenticationCaller requests use a gateway API key by default (Authorization: Bearer or x-api-key). Cloud management also uses admin/control-plane credentials.Cloudflare'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.
CostAISIX Cloud/commercial and infrastructure costs may apply; open-source deployment has hosting/operations costs.Cloudflare 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.
PermissionsA caller key cannot list/call tools until granted; access can be scoped to specific tools/servers/policies.The 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.
Data handlingThe gateway proxies MCP requests/responses between callers and upstream MCP servers, so sensitive tool payloads traverse the gateway boundary.Tool 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.
Limitations
Tradeoffs
  • Per-key tool grants are a strong least-privilege primitive
  • A gateway becomes a central trust boundary for credentials, upstream routing, and tool availability
  • 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.
Risk contextHigh. Central gateway compromise or misconfiguration can expose multiple upstream tools/credentials. Review admin-token handling, tenant separation, audit logging, rate limits, and emergency revocation.The 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.
Evidence date
Editorial review2026-09-112026-07-24
Candidate evidence2026-09-11T00:00:00.000Z2026-08-14T18:46:26.000Z

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

Read the evidence method →