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 fieldNetlify MCPShortlist candidateCloudflare MCPMCP100 Recommended
Task fit
Best for
  • Create, deploy, inspect, and configure applications hosted on Netlify.
  • Teams already using Netlify that can test with non-sensitive data and least privilege.
  • 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
  • Users who need an MCP100-recommended recommendation today
  • Unattended production workflows before permissions and failure behavior are 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
  • The connected data or account cannot be safely exposed to the selected AI client
  • You cannot verify least-privilege access and review write-capable tool calls
  • 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

Netlify · Publisher source ↗

First-party MCP

Cloudflare · Publisher source ↗

Maintenance
Maintenance details

Repo: Jul 28, 2026

Package: Jul 28, 2026

Repo: Sep 17, 2026

Package: Not documented

Popularity evidence
GitHub stars

63

GitHub stars · checked 2026-09-24T00:00:00.000Z

880

GitHub stars · checked 2026-09-24T04:14:26.352000Z

Package downloads / 30 days

15,719

package downloads / 30 days · checked 2026-07-29T17:30:00.000Z

No reliable download data
Client coverage
Client coverage details
Claude Code✓ Local stdio
Claude Desktop✓ Local stdio
Codex✓ Local stdio
VS Code✓ Local stdio
Cursor✓ Local stdio
OpenCode✓ Local stdio
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
AuthenticationAuthentication follows the publisher's documented endpoint or local-server configuration. OAuth scopes, API-key handling, and revocation behavior remain review items.Cloudflare's managed broad MCP endpoint is https://mcp.cloudflare.com/mcp and uses Cloudflare OAuth with Streamable HTTP. The older cloudflare/mcp-server-cloudflare family is domain-specific and is not this profile's canonical identity.
CostNo MCP100 cost conclusion is published yet. The publisher's account plan, API usage, infrastructure, or per-action charges may 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.
PermissionsExact permissions and the read/write boundary have not yet completed MCP100 independent review; consult the linked publisher sources and use the narrowest available scope.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 handlingPublisher-accessible account or application data may be returned to the MCP client and its selected model. Retention and subprocess behavior require candidate-specific review.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
  • First-party provenance and a clear task improve confidence, but do not replace an independent permissions and usability review.
  • Client transport compatibility does not prove that authentication, scopes, failure handling, and every tool behave safely.
  • 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 contextUse a test workspace or non-production account, least privilege, read-only controls where available, explicit approval for mutations, and credential revocation after evaluation.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-07-242026-07-24
Candidate evidence2026-09-24T00:00:00.000Z2026-09-24T04:25:05.554391Z

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

Read the evidence method →