M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionBigQuery MCP ServerSecure, read-only access to BigQuery for LLMs.MCP Toolbox for DatabasesGoogle's official database MCP toolbox — define AI-accessible database tools via config
FMRS62 / 100 · C74 / 100 · B
Reliability8 / 2013 / 20
Security and permissions16 / 2013 / 20
Maintenance10 / 2017 / 20
Documentation15 / 2016 / 20
Setup experience13 / 2015 / 20
Best for
  • Developers and analysts who want to query BigQuery quickly via AI assistants
  • Organizations that need to prevent AI agents from modifying data
  • Environments with sensitive data that require field-level access restrictions
  • Teams that want precise control over which database operations an AI can perform, rather than open arbitrary SQL execution
  • Scenarios needing a unified MCP setup across multiple database engines
Not for
  • Scenarios requiring write, update, or delete operations
  • Users who need unrestricted access to all columns
  • Strict security environments that cannot tolerate data leaving the network (since results are sent to LLM providers)
  • Lightweight cases that just want to run a few ad-hoc SQL queries without maintaining a tools.yaml config (a simpler single-database MCP may be a better fit)
Required permissions
  • BigQuery read permissions (e.g., roles/bigquery.user or roles/bigquery.dataViewer)
  • For service account auth, access to the service account key file
  • For advanced features, permission to list datasets and tables, and run dry-run queries
  • Database credentials (username/password/connection string) are supplied via env vars or config
  • A tool's actual permission is whatever SQL statement is defined in tools.yaml — designed for least privilege, but misconfiguration can still over-expose access
Risks and side effects
  • Data exfiltration: query results are sent to LLM providers (Anthropic, OpenAI) and may leave your network
  • Despite field restrictions, AI agents may attempt to infer data through crafted queries
  • Misconfiguration may weaken restrictions, e.g., incorrectly setting preventedFields or maximum bytes billed
  • If tools.yaml defines SQL statements that allow unconstrained writes or deletes, the AI could accidentally modify data
  • The prebuilt toolsets (--prebuilt) favor convenience and may expose broader query capability than a specific business actually needs — use a custom tools.yaml in production
Supported clientsClaude Desktop, Claude CodeClaude Code, Gemini CLI, Zed, Antigravity
Tools00