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 fieldGoogle Cloud Firestore MCPShortlist candidateGoogle MCP Toolbox for DatabasesMCP100 Recommended
Task fit
Best for
  • Firestore document inspection and project database operations
  • Use for Firestore-backed app debugging and data workflows.
  • Schema exploration and database-aware coding in development environments
  • Connecting one MCP layer to supported Google Cloud and third-party databases
  • Defining structured, parameterized database tools with integrated authentication and observability
Not ideal for
  • Official API exposes create, update and delete and database creation tools.
  • Unrestricted natural-language SQL against production data
  • Teams unwilling to operate and secure a local or hosted Toolbox process
Avoid when
  • Official API exposes create, update and delete and database creation tools.
  • The configured database user can modify production data or schema beyond the approved task
  • Sensitive query results cannot be sent to the AI client
  • Credentials would be committed in tools.yaml or MCP configuration
Provenance
Provenance details

First-party MCP

Google · Publisher source ↗

First-party MCP

Google · Publisher source ↗

Maintenance
Maintenance details

Repo: Not documented

Package: Not documented

Repo: Sep 24, 2026

Package: Not documented

Popularity evidence
GitHub starsNot documented

16,485

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

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
AuthenticationGoogle and Google Cloud remote MCP servers support user credentials or dedicated application credentials. OAuth 2.0 and IAM-principal based authentication are documented; Google Cloud MCP calls require MCP Tool User permission plus resource-specific IAM permissions.Authentication depends on the database source and can include database username/password, Google Cloud IAM, or other source-specific mechanisms. Use a dedicated read-only identity and secret manager or protected environment variables.
CostFirestore can charge for document reads/writes/deletes, index-entry reads, storage, bandwidth, backups/PITR and other operations. Free quota exists for some usage, but several features require billing.The Apache-licensed Toolbox and npm server have no documented MCP usage fee. Database services, Google Cloud resources, network transfer, observability backends, hosting, and the AI client may incur normal charges.
PermissionsEffective access is controlled by Google Cloud IAM. The Firestore MCP exposes both read and write/admin tools, including add/update/delete document, create/update/delete database, index operations, and backup/schedule operations.Effective permissions come from each configured database identity and the enabled prebuilt or custom tools. Generic prebuilt sets can include schema discovery and execute_sql; custom tools can constrain statements, parameters, and accessible sources.
Data handlingNot documented in the reviewed sources. The Firestore MCP reference does not make a separate MCP-specific retention or training claim; requests operate on Firestore resources under the authenticated Google Cloud identity.The Toolbox process connects directly to configured databases and returns selected schemas, rows, query results, and errors to the MCP client. Credentials may be supplied through environment variables or configuration; integrated cloud authentication and OpenTelemetry are available.
Limitations
Tradeoffs
  • API enablement/billing/scopes and remaining tools require check
  • Prebuilt tools are quick to adopt but may expose generic execute_sql capability; custom tools require more design but provide a narrower contract.
  • The npx path is convenient but the publisher recommends binary or container installation for standard reliable deployments.
  • Supporting many database engines increases configuration flexibility and operational complexity.
Risk contextThis is a write-capable database/admin MCP. Incorrect tool calls can change or delete documents, databases, indexes, backups, or schedules and can generate billable usage.Generic SQL tools can expose or mutate large amounts of data and retrieved database text can carry prompt-injection content. Prefer a non-production replica, read-only credentials, allow-listed custom parameterized tools, query limits, audit logs, and no secrets in config. 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 →