Back to the MCP Gateway catalog

MCP Gateway · Catalog

BigQuery icon

BigQuery MCP server

Official

BigQuery MCP is the official Model Context Protocol server for BigQuery, with OAuth and tools that let agents browse datasets and tables and run SQL, including read-only execution. Connect it through the Speakeasy MCP Gateway and agents such as Claude, Cursor, and ChatGPT get one governed URL for it, with SSO, RBAC, and a full audit trail.

Data & analytics6 toolsAuth: oauth

Behind the MCP Gateway

Run BigQuery MCP behind the MCP Gateway

One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every BigQuery call inspected and logged.

Deploy on MCP Gateway

Tools · 6

Each tool below can be allowed or denied per team and role at the MCP Gateway, and every call is inspected and logged.

list_dataset_ids

List BigQuery dataset IDs in a Google Cloud project.

get_dataset_info

Get metadata information about a BigQuery dataset.

list_table_ids

List table ids in a BigQuery dataset.

get_table_info

Get metadata information about a BigQuery table.

execute_sql_readonly

Run a read-only SQL query in the project and return the result. Prefer this tool over `execute_sql` if possible. This tool is restricted to only `SELECT` statements. `INSERT`, `UPDATE`, and `DELETE` statements and stored procedures aren't allowed. If the query doesn't include a `SELECT` statement, an error is returned. For information on creating queries, see the [GoogleSQL documentation](https://cloud.google.com/bigquery/docs/reference/standard-sql/query-syntax). Example Queries: -- Count the number of penguins in each island. SELECT island, COUNT(*) AS population FROM bigquery-public-data.ml_datasets.penguins GROUP BY island -- Evaluate a bigquery ML Model. SELECT * FROM ML.EVALUATE(MODEL `my_dataset.my_model`) -- Evaluate BigQuery ML model on custom data SELECT * FROM ML.EVALUATE(MODEL `my_dataset.my_model`, (SELECT * FROM `my_dataset.my_table`)) -- Predict using BigQuery ML model: SELECT * FROM ML.PREDICT(MODEL `my_dataset.my_model`, (SELECT * FROM `my_dataset.my_table`)) -- Forecast data using AI.FORECAST SELECT * FROM AI.FORECAST(TABLE `project.dataset.my_table`, data_col => 'num_trips', timestamp_col => 'date', id_cols => ['usertype'], horizon => 30) Queries executed using the `execute_sql_readonly` tool will have the job label `goog-mcp-server: true` automatically set. Queries are charged to the project specified in the `project_id` field.

execute_sql

Run a SQL query in the project and return the result. Prefer the `execute_sql_readonly` tool if possible. This tool can execute any query that bigquery supports including: * SQL Queries (SELECT, INSERT, UPDATE, DELETE, CREATE, etc.) * AI/ML functions like AI.FORECAST, ML.EVALUATE, ML.PREDICT * Any other query that bigquery supports. Example Queries: -- Insert data into a table. INSERT INTO `my_project.my_dataset`.my_table (name, age) VALUES ('Alice', 30); -- Create a table. CREATE TABLE `my_project.my_dataset`.my_table ( name STRING, age INT64); -- DELETE data from a table. DELETE FROM `my_project.my_dataset`.my_table WHERE name = 'Alice'; -- Create Dataset CREATE SCHEMA `my_project.my_dataset` OPTIONS (location = 'US'); -- Drop table DROP TABLE `my_project.my_dataset`.my_table; -- Drop dataset DROP SCHEMA `my_project.my_dataset`; -- Create Model CREATE OR REPLACE MODEL `my_project.my_dataset.my_model` OPTIONS ( model_type = 'LINEAR_REG' LS_INIT_LEARN_RATE=0.15, L1_REG=1, MAX_ITERATIONS=5, DATA_SPLIT_METHOD='SEQ', DATA_SPLIT_EVAL_FRACTION=0.3, DATA_SPLIT_COL='timestamp') AS SELECT col1, col2, timestamp, label FROM `my_project.my_dataset.my_table`; Queries executed using the `execute_sql` tool will have the job label `goog-mcp-server: true` automatically set. Queries are charged to the project specified in the `project_id` field.

Questions

What is a BigQuery MCP server?
A BigQuery MCP server exposes BigQuery to AI agents as Model Context Protocol tools. Instead of a custom integration per agent, any MCP client can connect to the server and call tools such as list_dataset_ids or get_dataset_info to work with BigQuery. The server in this catalog is the official BigQuery MCP server, which authenticates with OAuth.
What can you do with BigQuery MCP?
Agents can browse datasets and tables and run SQL, including read-only execution. The catalog lists 6 tools for this server, including list_dataset_ids, get_dataset_info, and list_table_ids. The full list with descriptions is on this page.
Why put BigQuery MCP behind an MCP gateway?
Connecting the BigQuery MCP server directly to each client means a separate credential per developer, no inventory of who can reach BigQuery through an agent, and no record of what agents did with it. An MCP gateway sits between every agent and the BigQuery server, so sign-in runs through your identity provider, role-based access decides which teams can call which BigQuery tools, and every call is inspected and logged in one place. The Speakeasy MCP Gateway applies those controls to BigQuery and to every other server in your catalog.
How do you connect BigQuery MCP through a gateway?
Add the BigQuery server from the Speakeasy MCP catalog and every agent reaches it through one gateway URL, next to the rest of your approved servers. Authentication uses OAuth 2.1 with PKCE and dynamic client registration, sign-in runs through your identity provider, and role-based access controls decide which teams can use which BigQuery tools. Every prompt, response, and tool call is inspected and logged at the gateway.
How is this different from an unofficial BigQuery MCP?
Community-built BigQuery MCP servers wrap the same BigQuery surface but are not vendor-maintained, and most authenticate with a static credential that gives an agent everything the credential owner can touch. This catalog lists the official BigQuery MCP server, which uses OAuth. Running it behind the Speakeasy MCP Gateway adds SSO, role-based access, and an audit trail of every call.

AI everywhere.

Control here.