Model Context Protocol (MCP) server that lets LLMs inspect BigQuery schemas and run SQL queries.
https://github.com/LucasHild/mcp-server-bigqueryStop copying and pasting SQL between your LLM chat and the BigQuery console. This MCP server connects Claude (or any MCP-compatible AI) directly to your BigQuery datasets, letting you explore schemas, run queries, and analyze data without leaving your conversation.
You're deep in a data analysis conversation with your LLM. You need to check a table schema, run a quick query, or validate some assumptions about your data. So you:
Every data professional knows this workflow. Every data professional hates it.
This MCP server eliminates the context switching. Your LLM can now:
No more tab switching. No more copy-paste workflows. Just seamless data analysis.
Schema Discovery: "Show me all tables in my analytics dataset and describe the user_events table structure." Your LLM gets the full picture instantly.
Ad-hoc Analysis: "Find the top 10 products by revenue last month." Your LLM writes the SQL, executes it against your actual data, and analyzes the results—all in one conversation.
Data Validation: "Check if we have any null values in the email column of our users table." No console switching required.
Query Optimization: Your LLM can examine table schemas, understand your data distribution, and suggest more efficient query patterns based on actual table structures.
The server handles Google Cloud authentication through service accounts—the same pattern you're already using for other BigQuery tools. Point it at your project and datasets:
# Install via Smithery (easiest)
npx -y @smithery/cli install mcp-server-bigquery --client claude
# Or configure manually in Claude Desktop
{
"mcpServers": {
"bigquery": {
"command": "uvx",
"args": [
"mcp-server-bigquery",
"--project", "your-gcp-project",
"--location", "us-central1"
]
}
}
}
Limit access to specific datasets with --dataset flags if you want to keep sensitive data separate.
This isn't about replacing your existing BigQuery tools—it's about removing friction from exploratory analysis and data conversations. Use it when you need quick insights, schema exploration, or iterative query development within an AI conversation.
Your existing BigQuery permissions, quotas, and security policies all apply. The server uses the same Google Cloud authentication you're already managing, so there's no additional security surface to worry about.
Built on the Model Context Protocol, so it works with Claude Desktop today and will work with other MCP-compatible tools as they emerge. The 100+ GitHub stars and active community contributions suggest this approach is resonating with other data professionals.
Ready to eliminate the BigQuery console shuffle from your data analysis workflow?