BigQuery MCP
Related Servers
Alternatives to BigQuery MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to query and analyze Google BigQuery data, including schema browsing, running queries, and comparing datasets through natural language.MIT
- FlicenseNot gradedqualityCmaintenanceEnables natural language interaction with BigQuery, providing tools to list tables, fetch schemas, and generate/execute queries via MCP.-
- AlicenseNot gradedqualityDmaintenanceEnables natural language exploration and querying of Google BigQuery datasets through four tools: listing datasets, inspecting table schemas, generating SQL queries with LLM assistance, and executing approved queries.1MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to analyze BigQuery datasets through MCP, using tools to inspect datasets and execute read-only SQL queries.-
- AlicenseNot gradedqualityCmaintenanceEnables LLMs to explore BigQuery datasets and tables, run safe read-only queries, and optionally perform vector search using BigQuery embeddings.10MIT
- FlicenseNot gradedqualityCmaintenanceEnables secure read-only interaction with Google BigQuery through natural language, including listing datasets, listing tables, retrieving metadata, and executing queries with cost controls.-
TDQS
Scored across 3 tools
Each tool has a distinct and clear purpose: query executes SQL, list_tables enumerates tables, and get_schema describes table structure. There is little risk of an agent selecting the wrong tool for a task.
list_tables and get_schema follow a consistent verb_noun snake_case pattern. The lone tool 'query' is a simple verb without a noun object, which is a minor deviation but still clear and natural for the operation.
Three tools is on the minimal side but reasonable for a focused BigQuery read/query server. Each tool serves a distinct need, though the server could support a slightly broader set without feeling bloated.
The query tool can execute arbitrary SQL, including DDL/DML, so most BigQuery operations are reachable indirectly. The main gaps are convenience features like listing datasets or managing query jobs, but agents can work around these with SQL and INFORMATION_SCHEMA queries.