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 fieldStackQL MCPWatchlist candidateCloudflare MCPMCP100 Selected
Task fit
Best for
  • Read-only cloud inventory and governed infrastructure queries
  • Teams that can enforce read_only or safe mode with audit logging
  • 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
  • Unattended infrastructure mutation without approval and audit
  • Organizations that cannot tightly scope cloud credentials by provider/account
  • A narrowly scoped integration when the broad Cloudflare API server is authorized with excessive permissions
  • Environments that cannot complete browser-based OAuth
Avoid when
  • You would run full_access with broad cloud credentials
  • You cannot review audit logs or enforce tool allowlists
  • 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

StackQL Studios · 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
AuthenticationUses provider credentials supplied to StackQL; authentication varies by cloud provider. The MCP transport itself can be stdio/HTTP/TLS depending on deployment.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.
CostOpen-source; cloud provider usage and hosting costs apply.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.
PermissionsServer mode controls mutation: read_only refuses writes; safe/default requires approval; delete_safe and full_access expand privileges. enabled_tools can narrow exposure.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 handlingCan read cloud inventory/configuration and, when permitted, mutate or invoke provider lifecycle operations. Audit logs can record calls.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
  • Default safe/read-only modes materially improve control
  • The same server can still become a powerful cloud control plane when escalated
  • 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. In full or writable modes the server can change cloud infrastructure. Keep read_only/safe defaults, least-privileged provider credentials, and audit logging.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 →