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 candidateTerraform MCPMCP100 Recommended
Task fit
Best for
  • Firebase project and app development with Firebase CLI
  • Use for Firebase project setup, development and diagnostics.
  • Connect compatible AI clients to HashiCorp's documented MCP capabilities.
Not ideal for
  • The real official implementation is part of firebase-tools; the separate registry label must not become a second duplicate entry.
  • Users who need a fully reviewed MCP100 recommendation today
Avoid when
  • The real official implementation is part of firebase-tools; the separate registry label must not become a second duplicate entry.
  • Permissions, credentials, and connected data cannot be tested with least privilege
Provenance
Provenance details

First-party MCP

Google / Firebase · Publisher source ↗

First-party MCP

HashiCorp · Publisher source ↗

Maintenance
Maintenance details

Repo: Not documented

Package: Not documented

Repo: Aug 14, 2026

Package: Not documented

Popularity evidence
GitHub starsNot documented

1,534

GitHub stars · checked 2026-09-25T18:35:00Z

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✓ Local stdio
Claude Desktop✓ Local stdio
Codex✓ Local stdio
VS Code✓ Local stdio
Cursor✓ Local stdio
OpenCode✓ Local stdio
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.HCP Terraform/TFE API tokens; remote client may pass per-user TFE_TOKEN
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.HCP/TFE/run costs may 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.HCP Terraform/TFE RBAC
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.registry/HCP/TFE data may reach connected MCP client/LLM
Limitations
Tradeoffs
  • Tool surface is selected by feature group and CLI version; published list is source-supported, not live authenticated runtime enumeration.
  • Publisher attribution supports discovery, but does not replace an independent permissions and usability review.
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.stdio/localhost defaults; strict CORS; TLS verify on; rate limits; ENABLE_TF_OPERATIONS=false by default
Evidence date
Editorial review2026-10-192026-07-24
Candidate evidence2026-10-192026-09-25T18:35:00Z

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

Read the evidence method →