Google BigQuery, verified
MCP server by Google Cloud · Verified
List datasets, inspect tables and run SQL queries in Google BigQuery projects, with job status and cancellation.
Connect to Google BigQuery
Google BigQuery needs sign-in. Connect with its own URL:
Your client opens Google Cloud’s sign-in the first time you use it. The token stays between your client and Google Cloud.
Share this server
Opens this page, with the URL and setup steps.
mcp.tc/i/bigqueryAbout
Connects an assistant to Google BigQuery. It can list datasets and tables, read their metadata (including BigLake namespaces and tables), run SQL queries, fetch paged results and check or cancel query jobs.
It runs as a hosted streamable HTTP endpoint at bigquery.googleapis.com/mcp. Access uses Google OAuth 2.0 and IAM permissions on the target project. The read-only SQL tool is limited to SELECT statements, while the general SQL tool can run statements that change data.
What you can do
- List dataset IDs and BigLake namespaces in a project
- Read metadata for datasets and tables
- List table IDs in a dataset
- Run read-only SELECT queries
- Run any SQL statement, including writes and DDL
- Page through results of long-running query jobs
- Check job status and cancel running jobs
Tools 9
list_dataset_idsRead-onlyList BigQuery dataset IDs and BigLake namespaces in a project, with pagination.
get_dataset_infoRead-onlyGet metadata about a BigQuery dataset or BigLake namespace.
list_table_idsRead-onlyList table IDs in a dataset or BigLake namespace, with pagination.
get_table_infoRead-onlyGet metadata about a BigQuery table or BigLake table.
execute_sql_readonlyRead-onlyRun a read-only SELECT query in the project and return the result.
execute_sqlCan deleteRun any BigQuery SQL, including INSERT, UPDATE, DELETE, CREATE and ML functions.
get_query_resultsRead-onlyPoll or paginate results of a query job by job ID.
cancel_jobCan deleteCancel a running BigQuery job.
get_jobRead-onlyGet status, statistics and configuration of a BigQuery job.
Read from the live server on 17 Nov 2026. Read-only, Writes and Can delete are hints the server declares; your client decides whether to ask before running a tool.
Example prompts
List the datasets in my project my-analytics-prod
Show the schema of the orders table in the sales dataset
Run a query for daily signups over the last 30 days
Check the status of my last BigQuery job and cancel it if it is still running
Set up
Every client connects to bigquery.googleapis.com, and Google Cloud asks you to sign in the first time. Pick yours; the page remembers your choice.
Claude Code
- Run this in a terminal, in your project folder:
claude mcp add --transport http bigquery https://bigquery.googleapis.com/mcp- Start Claude Code, type
/mcp, pick bigquery and choose Authenticate. A browser window opens for the Google Cloud sign-in.
Add --scope user to make it available in every project, not just this one.
Claude Desktop
- Open Customize → Connectors, click + Add, then Add custom connector.
- Name it Google BigQuery and paste this URL:
https://bigquery.googleapis.com/mcp- Click Add, then Connect, and sign in when Google Cloud asks.
Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.
claude.ai
- Open the connector form on claude.ai. This button fills in the name and URL for you:
Add to claude.ai (opens in a new tab)
- Check that the URL reads
https://bigquery.googleapis.com/mcpand click Add. - Click Connect and sign in when Google Cloud asks.
Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.
ChatGPT
- On chatgpt.com, go to Plugins, select +, then Add custom MCP server.
- Enter a name for the server.
- Under Connection, paste
https://bigquery.googleapis.com/mcpas the server URL, then for authentication choose OAuth. ChatGPT sends you to Google Cloud to sign in. - Check I understand and want to continue, then select Create as a plugin.
Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).
Cursor
Add to Cursor (opens in a new tab)
Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):
{
"mcpServers": {
"bigquery": {
"url": "https://bigquery.googleapis.com/mcp"
}
}
}Cursor shows Needs authentication next to the server. Click the button beside it to sign in.
VS Code
Install in VS Code (opens in a new tab)
Or from a terminal:
code --add-mcp '{"name":"bigquery","type":"http","url":"https://bigquery.googleapis.com/mcp"}'Or commit it to the repo in .vscode/mcp.json:
{
"servers": {
"bigquery": {
"type": "http",
"url": "https://bigquery.googleapis.com/mcp"
}
}
}VS Code asks you to sign in the first time the server starts.
Devin Desktop
- Add it to
~/.config/devin/mcp_config.json(macOS and Linux) or%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"bigquery": {
"serverUrl": "https://bigquery.googleapis.com/mcp"
}
}
}- Refresh the MCP server list in Cascade and sign in when asked.
Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.
Codex
codex mcp add bigquery --url https://bigquery.googleapis.com/mcp
codex mcp login bigqueryOr edit ~/.codex/config.toml directly:
[mcp_servers.bigquery]
url = "https://bigquery.googleapis.com/mcp"Gemini CLI
gemini mcp add --transport http bigquery https://bigquery.googleapis.com/mcpThen, inside Gemini CLI, run /mcp auth bigquery to sign in.
This adds it to the current project. Add -s user to use it everywhere.
Any client
Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI’s settings file.
{
"mcpServers": {
"bigquery": {
"type": "http",
"url": "https://bigquery.googleapis.com/mcp"
}
}
}Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.
Client only starts local servers? Bridge it with npx -y mcp-remote https://bigquery.googleapis.com/mcp.
Embed
Show Google BigQuery in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work
The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.
README badge
[](https://mcp.tc/i/bigquery)<a href="https://mcp.tc/i/bigquery"><img src="https://mcp.tc/i/bigquery/badge.svg" alt="Google BigQuery on mcp.tc" height="20"></a>It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.
Website card
<script src="https://mcp.tc/w/bigquery.js" async></script>The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.
iframe
<iframe src="https://mcp.tc/embed/bigquery" title="Google BigQuery on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.
JSON
The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).
https://mcp.tc/i/bigquery.jsonAI prompt
Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the Google BigQuery card to your site.
Add the mcp.tc card for Google BigQuery, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.
Put this tag where the card should appear. The card renders right before it:
```html
<script src="https://mcp.tc/w/bigquery.js" async></script>
```
To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.
```html
<div data-mcptc="bigquery"><a href="https://mcp.tc/i/bigquery">Google BigQuery on mcp.tc</a></div>
```
Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.
If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).
For a README or other Markdown docs, use the badge instead:
```markdown
[](https://mcp.tc/i/bigquery)
```
Reference: https://mcp.tc/embedChange history
We read this server’s tool list every 3 hours and record what changes. Last read 18 Nov 2026, 05:33 UTC.
-
9 tools changed.
Details, 10 Nov 2026, 14:48 UTC
Changed 9
cancel_jobdescription and output schemaBeforeCancel a running BigQuery job. Use this tool to cancel a query job that is currently executing (i.e. returned
`job_complete:false` with a`job_id`from `execute_sql` or `execute_sql_readonly`). Specify the`job_id`to abort.AfterCancel a running BigQuery job. Use this tool to cancel a query job that is currently executing (i.e. returned `jobComplete: false` with a `jobId` from `execute_sql` or `execute_sql_readonly`). Specify the `jobId` to abort.
execute_sqldescription and output schemaThe text shown here is the same before and after: the change is past the first 1,000 characters or in characters that don’t show.
execute_sql_readonlydescription and output schemaThe text shown here is the same before and after: the change is past the first 1,000 characters or in characters that don’t show.
get_dataset_infooutput schemaget_jobdescription and output schemaBeforeGet information and status about a BigQuery job. Use this tool to check the status, statistics, or configuration of a job using its
`job_id`.AfterGet information and status about a BigQuery job. Use this tool to check the status, statistics, or configuration of a job using its `jobId`.
get_query_resultsdescription, input schema and output schemaBeforeGet the results of a BigQuery SQL query job. Use this tool ONLY when: 1. A previous `execute_sql` or `execute_sql_readonly` call returned
`job_complete:false` with a`job_id`(poll with this tool until`job_complete:true`), OR 2. You need to paginate through additional rows using`page_token`or`start_index`for a previously completed job. Do NOT call this tool if the query already returned`job_complete:true` with allrows.Supports pagination. Use`max_results`to limit results and`page_token`to retrieve the next page of results.AfterGet the results of a BigQuery SQL query job. Use this tool ONLY when: 1. A previous `execute_sql` or `execute_sql_readonly` call returned `jobComplete: false` with a `jobId` (poll with this tool until `jobComplete: true`), OR 2. You need to paginate through additional rows using `pageToken` or `startIndex` for a previously completed job. Do NOT call this tool if the query already returned `jobComplete: true` with all rows (no `pageToken`). Supports pagination. Use `maxResults` to limit results (3,000 by default) and `pageToken` to retrieve the next page of results. A response has a `pageToken` only when more rows are available.
- Description of
maxResultsBeforeOptional. Maximum number of results to read.
AfterOptional. Maximum number of results to read. Defaults to 3,000.
- Description of
get_table_infooutput schemalist_dataset_idsdescriptionBeforeList BigQuery dataset IDs and BigLake namespaces in a Google Cloud project. Supports pagination. Use
`page_size`to limit results and`page_token`to retrieve next page.AfterList BigQuery dataset IDs and BigLake namespaces in a Google Cloud project. Supports pagination. Use `pageSize` to limit results and `pageToken` to retrieve next page.
list_table_idsdescriptionBeforeList table ids in a BigQuery dataset or BigLake namespace. Supports pagination. Use
`page_size`to limit results and`page_token`to retrieve next page.AfterList table ids in a BigQuery dataset or BigLake namespace. Supports pagination. Use `pageSize` to limit results and `pageToken` to retrieve next page.
-
7 tools changed.
Details, 4 Nov 2026, 08:45 UTC
Changed 7
cancel_joboutput schemaexecute_sqldescription and output schemaThe text shown here is the same before and after: the change is past the first 1,000 characters or in characters that don’t show.
execute_sql_readonlydescription and output schemaThe text shown here is the same before and after: the change is past the first 1,000 characters or in characters that don’t show.
get_dataset_infooutput schemaget_joboutput schemaget_query_resultsdescription, input schema and output schemaBeforeGet the results of a BigQuery SQL query job. Use this tool ONLY when: 1. A previous `execute_sql` or `execute_sql_readonly` call returned `job_complete: false` with a `job_id` (poll with this tool until `job_complete: true`), OR 2. You need to paginate through additional rows using `page_token` or `start_index` for a previously completed job. Do NOT call this tool if the query already returned `job_complete: true` with all
rows (no `page_token`).Supports pagination. Use`maxResults`to limit results(3,000 by default)and `page_token` to retrieve the next page of results.A response has a `page_token` only when more rows are available.AfterGet the results of a BigQuery SQL query job. Use this tool ONLY when: 1. A previous `execute_sql` or `execute_sql_readonly` call returned `job_complete: false` with a `job_id` (poll with this tool until `job_complete: true`), OR 2. You need to paginate through additional rows using `page_token` or `start_index` for a previously completed job. Do NOT call this tool if the query already returned `job_complete: true` with all rows. Supports pagination. Use `max_results` to limit results and `page_token` to retrieve the next page of results.
- Description of
maxResultsBeforeOptional. Maximum number of results to read.
Defaults to 3,000.AfterOptional. Maximum number of results to read.
- Description of
get_table_infooutput schema
-
6 tools changed.
Details, 1 Nov 2026, 23:38 UTC
Changed 6
cancel_joboutput schemaexecute_sqldescription and output schemaThe text shown here is the same before and after: the change is past the first 1,000 characters or in characters that don’t show.
execute_sql_readonlydescription and output schemaThe text shown here is the same before and after: the change is past the first 1,000 characters or in characters that don’t show.
get_joboutput schemaget_query_resultsdescription, input schema and output schemaBeforeGet the results of a BigQuery SQL query job. Use this tool ONLY when: 1. A previous `execute_sql` or `execute_sql_readonly` call returned `job_complete: false` with a `job_id` (poll with this tool until `job_complete: true`), OR 2. You need to paginate through additional rows using `page_token` or `start_index` for a previously completed job. Do NOT call this tool if the query already returned `job_complete: true` with all
rows.Supports pagination. Use`max_results`to limit results and `page_token` to retrieve the next page of results.AfterGet the results of a BigQuery SQL query job. Use this tool ONLY when: 1. A previous `execute_sql` or `execute_sql_readonly` call returned `job_complete: false` with a `job_id` (poll with this tool until `job_complete: true`), OR 2. You need to paginate through additional rows using `page_token` or `start_index` for a previously completed job. Do NOT call this tool if the query already returned `job_complete: true` with all rows (no `page_token`). Supports pagination. Use `maxResults` to limit results (3,000 by default) and `page_token` to retrieve the next page of results. A response has a `page_token` only when more rows are available.
- Description of
maxResultsBeforeOptional. Maximum number of results to read.
AfterOptional. Maximum number of results to read. Defaults to 3,000.
- Description of
get_table_infooutput schema
-
1 tool changed.
Details, 27 Oct 2026, 15:01 UTC
Changed 1
get_dataset_infooutput schema
-
1 tool changed.
Details, 25 Oct 2026, 14:46 UTC
Changed 1
get_table_infooutput schema
-
2 tools changed.
Details, 21 Oct 2026, 04:36 UTC
Changed 2
cancel_joboutput schemaget_joboutput schema
-
3 tools changed.
Details, 19 Oct 2026, 07:37 UTC
Changed 3
execute_sqldescription and output schemaThe text shown here is the same before and after: the change is past the first 1,000 characters or in characters that don’t show.
execute_sql_readonlydescription and output schemaThe text shown here is the same before and after: the change is past the first 1,000 characters or in characters that don’t show.
get_query_resultsoutput schema
-
3 tools changed.
Newly required parameter
Details, 12 Oct 2026, 16:30 UTC
Changed 3
cancel_jobinput schema- Now required:
location - Description of
locationBeforeOptional.The geographic location of the job.AfterRequired. The geographic location of the job.
- Now required:
get_jobinput schema- Now required:
location - Description of
locationBeforeOptional.The geographic location of the job.AfterRequired. The geographic location of the job.
- Now required:
get_query_resultsinput schema- Now required:
location - Description of
locationBeforeOptional.The geographic location of the job.AfterRequired. The geographic location of the job.
- Now required:
-
Tracking started: 9 tools.
FAQ
Can I paste mcp.tc/i/bigquery into my MCP client?
No. mcp.tc links are pages, not server addresses. Connect with https://bigquery.googleapis.com/mcp, so your client talks to Google BigQuery directly. The sign-in token only works there anyway. The quick link is for sharing: it opens this page, with setup steps for every client.
Does Google BigQuery need an API key or a sign-in?
Yes, you need a Google Cloud account. The first time your client connects, it opens Google Cloud’s sign-in page. The token goes straight to the server’s own URL, never through mcp.tc.
Is Google BigQuery a remote or a local server?
Remote. Google Cloud hosts it at https://bigquery.googleapis.com/mcp, and it speaks Streamable HTTP. There’s nothing to install.
What can Google BigQuery do?
It has 9 tools, including list_dataset_ids, get_dataset_info and list_table_ids. You can list dataset IDs and BigLake namespaces in a project, read metadata for datasets and tables and list table IDs in a dataset.
Which clients can use it?
Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.
Does mcp.tc track changes to Google BigQuery?
Yes. Google BigQuery’s History tab shows each change we find to its tools, down to descriptions and parameters, plus new versions and edits by its owner. Follow the listing to get an email when it changes.
Who wrote this page?
mcp.tc’s robot read Google BigQuery’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.
mcp.tc isn’t affiliated with Google Cloud. This page was built from Google BigQuery’s public metadata, last checked on 17 Nov 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.