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 fieldDoiT MCP ServerShortlist candidateGoogle MCP Toolbox for DatabasesMCP100 Recommended
Task fit
Best for
  • Analyze cloud spend, FinOps data and DoiT platform information from MCP clients
  • Analyze cloud spend, FinOps data and DoiT platform information from MCP clients.
  • 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
  • Cloud-cost and billing data can be commercially sensitive. Access follows DoiT API permissions; use scoped identities and avoid exposing personal API tokens in prompts or repositories.
  • Unrestricted natural-language SQL against production data
  • Teams unwilling to operate and secure a local or hosted Toolbox process
Avoid when
  • Cloud-cost and billing data can be commercially sensitive. Access follows DoiT API permissions; use scoped identities and avoid exposing personal API tokens in prompts or repositories.
  • 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

DoiT · 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 stars

13

GitHub stars · checked 2026-10-20

16,485

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

Package downloads / 30 days

6,935

package downloads / 30 days · checked 2026-10-20

No reliable download data
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
AuthenticationOAuth for the hosted Streamable HTTP endpoint; headless remote clients can use a customer personal API token as Bearer auth; local stdio uses `DOIT_API_KEY`.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.
CostThe user's DoiT plan must include API access; no separate MCP-specific price is stated in the reviewed repository.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.
PermissionsTools follow the same permissions as the DoiT API identity/token. The user's DoiT plan must include API access.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 handlingTools can retrieve commercially sensitive cloud-cost, invoice, anomaly, and account data. The local server emits payload-free response metrics that exclude tool arguments and response bodies.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
  • Shortlist evidence is sufficient for identity, setup and task value; authenticated runtime tool-schema measurement and exhaustive security certification remain out of scope.
  • 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 contextThe server includes generated/handwritten DoiT API tools and can perform writes where the DoiT API permits them. Cloud-cost and billing data is commercially sensitive.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-202026-09-24T04:25:05.554391Z

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

Read the evidence method →