MCP Gateway · Claude
Connect BigQuery to Claude
Analysts are not the only people with questions for the warehouse. With BigQuery behind the Speakeasy MCP Gateway, anyone in Claude can find the table that holds an answer, understand its columns and get a result from read-only SQL that Claude writes for them. Each person only sees the servers their role can reach.
- Category
- Data & analytics
- Tools
- 6
- Authentication
- OAuth
- Claude
- Web, desktop and mobile
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.
Before you start
What BigQuery needs first
A Google Cloud project administrator with IAM admin access does the BigQuery side of the setup.
- You need a Google Account that can administer the project and create OAuth credentials.
- Granting roles needs IAM admin access, such as Project IAM Admin.
- Billing is optional for initial setup.
- External apps in Testing allow at most 100 test users, and authorizations expire after seven days.
In BigQuery
- Enable the BigQuery API in the project.
- Grant each user MCP Tool User, BigQuery Job User, and BigQuery Data Viewer.
- Configure the OAuth consent screen as Internal or External.
- For External apps, add the BigQuery scope and test users, or publish the app.
- Create an OAuth client and copy its credentials.
Set up
Add BigQuery to Claude in 4 steps
- 01
Add BigQuery from the catalog
An admin finds BigQuery in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.
BigQuery uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.
Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.
- 02
Choose who can use BigQuery
Give teams the
mcp:connectscope on the BigQuery server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds BigQuery to their gateway on the next call, and removing it takes it away. - 03
Connect Claude
Add the gateway URL as a custom connector, then connect it from Customize > Connectors.
On Team and Enterprise plans, an Owner opens Organization settings > Connectors, chooses Add > Custom > Web and pastes the gateway URL.
Each person opens Customize > Connectors and clicks Connect to sign in.
On Pro and Max plans, each person adds it themselves under Customize > Connectors, with + Add > Add custom connector.
- 04
Sign in and use BigQuery from Claude
The first time Claude connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
BigQuery needs its own OAuth grant, so each person connects it once. Until they do, BigQuery calls fail while the rest of the gateway keeps working.
From then on, BigQuery's tools appear in Claude, limited to what the person's access allows, and every call lands in the gateway's tool logs.
No client ID or secret is needed: the gateway's sign-in handles client registration. Each person only sees the servers their role can reach.
Use cases
What Claude users do with BigQuery
Ask a data question in plain words
Ask how many orders shipped late last month, and Claude writes the SQL, runs it read-only and explains the answer in a sentence or two.
Find where the data lives
Not sure which table holds customer signups? Claude lists the datasets and tables in the project and suggests the likely one.
Understand what a table contains
Before trusting a number, ask Claude to describe a table's columns and metadata in plain language, so you know what each field means.
Tools
6 tools
Each BigQuery tool can be allowed or denied per team and role at the MCP Gateway before Claude sees it.
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.
execute_sql
Run a SQL query in the project and return the result. Prefer the execute_sql_readonly tool if possible.
Control
What Speakeasy can see and stop in Claude
The gateway covers every client the same way. The rest depends on what Claude exposes to Speakeasy.
Tool logs
Gateway
Every BigQuery call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the BigQuery tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to BigQuery can reject a tool request before it reaches the server, or withhold a result from Claude. MCP-scoped policies are enabled per organization.
Anthropic inference hooks
Claude
On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.
Conversation import
Claude
Claude conversations can be imported through Anthropic's Compliance API for review after the fact.
- Custom connectors need a Claude plan that supports them.
- Budgets don't cover Claude web and desktop usage.
Questions
Frequently asked questions
Can people in Claude change data in BigQuery?
Do prompts that query BigQuery get checked in Claude?
How do Claude users get BigQuery?
Are BigQuery calls from Claude logged?
Connect more