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.
| Evidence field | BifrostShortlist candidate | Cloudflare MCPMCP100 Recommended |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | First-party MCP github:maximhq · Publisher source ↗ | First-party MCP Cloudflare · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Not documented Package: Not documented | Repo: Sep 17, 2026 Package: Not documented |
| Popularity evidence | ||
| GitHub stars | Not documented | 880 GitHub stars · checked 2026-09-24T04:14:26.352000Z |
| Shared repository stars | 9,002 Shared repository stars (not MCP-specific) · checked 2026-10-21 | Not documented |
| Shared-package downloads / 30 days | 4,088 shared-package downloads / 30 days (not MCP-specific) · checked 2026-10-21 | Not documented |
| Client coverage | ||
| Client coverage details | Not documented | Claude Code✓ Streamable HTTP Claude Desktop✓ Streamable HTTP Codex✓ Streamable HTTP VS Code✓ Streamable HTTP Cursor✓ Streamable HTTP OpenCode✓ Streamable HTTP |
| Client coverage note | Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server. | |
| Access and data | ||
| Authentication | Supports Bifrost access-control mechanisms such as virtual keys and OAuth2 as documented by the product. | 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. |
| Cost | Open-source/managed Bifrost and underlying model/service usage may have separate 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. |
| Permissions | Roles, virtual keys and tool scoping can constrain the upstream MCP surface; upstream server permissions still apply. | 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 handling | MCP requests and telemetry pass through the Bifrost gateway; deployment and telemetry configuration determine retention. | 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 |
|
|
| Risk context | MCP-specific adoption and independent operational evidence are still emerging relative to established Recommended gateways. | 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 review | 2026-10-21 | 2026-07-24 |
| Candidate evidence | 2026-10-21T00:00:00Z | 2026-09-24T04:25:05.554391Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →