Google Cloud documents a remote BigQuery Model Context Protocol server at docs.cloud.google.com/bigquery/docs/use-bigquery-mcp, enabled when the BigQuery API is enabled. Connect MCP clients to the managed HTTP endpoint `https://bigquery.googleapis.com/mcp` with OAuth 2.0 and IAM (API keys are not accepted). Documented IAM roles include MCP Tool User (`roles/mcp.toolUser`), BigQuery Job User (`roles/bigquery.jobUser`), and BigQuery Data Viewer (`roles/bigquery.dataViewer`). Tools include `execute_sql` and `execute_sql_readonly` per the use guide; `execute_sql_readonly` allows only read-only operations while `execute_sql` is the sole non-read-only tool. Limitations documented: query processing capped at three minutes by default, results limited to 3,000 rows, and Google Drive external tables unsupported for those SQL tools.
Use cases
- Let agents list datasets and run read-only SQL against BigQuery warehouses
- Prototype conversational analytics over SAP Business Data Cloud Connect + BigQuery pipelines
- Build workflows that trigger actions from BigQuery insights via MCP clients
- Use forecasting sample prompts documented in Google Cloud BigQuery MCP guide
- Restrict write access with IAM deny policies on the execute_sql tool
Key features
- Claude Desktop
- Cursor
- Gemini CLI
- ChatGPT
Frequently Asked Questions
- Is this the same as the local BigQuery MCP server?
- Google Cloud docs distinguish the remote managed server from a local stdio MCP for custom parameterized SQL tools.
- Can agents run write SQL?
- Only via execute_sql; execute_sql_readonly blocks DML/DDL/Python UDFs. Deny policies can block execute_sql.
- What are the query limits?
- Docs cite a default three-minute processing cap and 3,000-row result limit for execute_sql tools.
Related
Related
3 Indexed items
ClickHouse Cloud Remote MCP Server
ClickHouse documents a fully managed remote Model Context Protocol server for ClickHouse Cloud at clickhouse.com/docs/cloud/features/ai-ml/remote-mcp. Connect MCP clients to the HTTP endpoint `https://mcp.clickhouse.cloud/mcp` with OAuth 2.0 (browser sign-in with ClickHouse Cloud credentials; no separate API key required per docs). Agents can list databases and tables, inspect schemas, and run scoped read-only SELECT queries; the remote server also exposes richer ClickHouse Cloud integration such as service management, backup monitoring, ClickPipe visibility, and billing data per ClickHouse docs. Enable per service in the Cloud console (Connect → MCP). For self-hosted ClickHouse, ClickHouse maintains the separate open-source mcp-clickhouse project—distinct from this Cloud remote MCP.
MotherDuck MCP Server
MotherDuck documents a remote Model Context Protocol server at motherduck.com/docs/sql-reference/mcp hosted at `https://api.motherduck.com/mcp` with OAuth (or Bearer token) and read-write SQL access to MotherDuck cloud databases. Tools include `list_databases`, `list_tables`, `list_columns`, `search_catalog`, `query`, `query_rw`, `ask_docs_question`, Dive tools (`list_dives`, `read_dive`, `view_dive`, `save_dive`, etc.), and Flight scheduling tools (`list_flights`, `create_flight`, `run_flight`, etc.) per MotherDuck MCP docs. For local DuckDB files or custom configs, MotherDuck points to the open-source `mcp-server-motherduck` package (`uvx mcp-server-motherduck --db-path md:`) on github.com/motherduckdb/mcp-server-motherduck.
MotherDuck MCP Server
MotherDuck documents a remote Model Context Protocol server at `https://api.motherduck.com/mcp` (fully managed, read-write) that lets Claude, ChatGPT, Cursor, Claude Code, Codex, and other MCP clients query MotherDuck cloud databases via OAuth or Bearer tokens with zero local install per motherduck.com/docs/sql-reference/mcp. Remote tools include read-only `query` and read-write `query_rw` plus schema exploration helpers documented in the MCP workflows guide. For local DuckDB files, S3 paths, or custom limits, the open-source `mcp-server-motherduck` package (motherduckdb/mcp-server-motherduck on GitHub, PyPI `mcp-server-motherduck`) runs via `uvx` with flags such as `--db-path`, `--motherduck-token`, and `--read-write` for self-hosted stdio or HTTP transports.