BigQuery MCP
Related Servers
Alternatives to BigQuery MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables LLMs to inspect database schemas, list tables, and execute SQL queries against Google's BigQuery analytics platform.-
- FlicenseNot gradedqualityAmaintenanceEnables LLMs to inspect schemas, list and describe tables, and execute SQL queries against configured Google BigQuery datasets.-
- FlicenseNot gradedqualityAmaintenanceEnables LLMs to inspect database schemas, list and describe tables, and execute SQL queries against BigQuery using BigQuery dialect.-
- FlicenseNot gradedqualityAmaintenanceEnables LLMs to inspect database schemas, list and describe tables, and execute SQL queries against BigQuery.-
- FlicenseNot gradedqualityAmaintenanceEnables LLMs to inspect database schemas, list tables, describe table schemas, and execute SQL queries against BigQuery.-
- FlicenseNot gradedqualityAmaintenanceEnables LLMs to inspect database schemas, list tables, and execute SQL queries against BigQuery.-
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.