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 fieldFirebase MCPShortlist candidateCloudflare MCPMCP100 Recommended
Task fit
Best for
  • Firebase project and app development with Firebase CLI
  • Use for Firebase project setup, development and diagnostics.
  • 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
  • The real official implementation is part of firebase-tools; the separate registry label must not become a second duplicate entry.
  • 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 real official implementation is part of firebase-tools; the separate registry label must not become a second duplicate entry.
  • 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

Google / Firebase · 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 starsNot documented

880

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

Shared repository stars

4,477

Shared repository stars (not MCP-specific) · checked 2026-10-20

Not documented
Shared-package downloads / 30 days

12,906,051

shared-package downloads / 30 days (not MCP-specific) · checked 2026-10-20

Not documented
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
AuthenticationThe Firebase MCP runs locally through firebase-tools and uses the same credentials as the Firebase CLI: either a logged-in user or Application Default Credentials depending on the environment.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.
CostThere is no separate MCP fee documented. Firebase has no-cost Spark allowances and pay-as-you-go Blaze usage; several Firebase/Google Cloud services can incur charges beyond free quotas.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.
PermissionsThe MCP can only act with the Firebase/Google Cloud permissions of the authenticated CLI identity. Firebase describes the tools as operating directly on the user's Firebase project with approval.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 handlingNot documented in the reviewed sources. The reviewed Firebase MCP page does not state MCP-specific retention/training behavior; the MCP runs locally and accesses Firebase services using the local CLI identity.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
  • Tool surface is selected by feature group and CLI version; published list is source-supported, not live authenticated runtime enumeration.
  • 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 contextThe MCP exposes project operations through the same authority as firebase-tools. Depending on enabled tool groups, it can affect project configuration, deployed resources, rules, data, and billable services.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-10-192026-07-24
Candidate evidence2026-10-192026-09-24T04:25:05.554391Z

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

Read the evidence method →