Chroma’s official MCP server: vector search and collection management for RAG workflows.
Google BigQuery is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Google-managed remote MCP server for listing BigQuery datasets/tables and running SQL analytics.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http google-bigquery-mcp https://bigquery.googleapis.com/mcp
# 2 — ask your agent for something these tools do
# list_dataset_ids, get_dataset_info, list_table_ids and 3 more
Google BigQuery costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http google-bigquery-mcp https://bigquery.googleapis.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
6 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List BigQuery dataset IDs in a Google Cloud project. Supports pagination. Use page_size to limit results and page_token to retrieve next page.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| pageSize | integer | no | Optional. The maximum number of results to return in a single response page. If unset, the default page size of 5000 is used. |
| pageToken | string | no | Optional. Page token, returned by a previous call, to request the next page of results. |
| projectId | string | yes | Required. Project ID of the dataset request. |
Get metadata information about a BigQuery dataset.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| datasetId | string | yes | Required. Dataset ID of the dataset request. |
| projectId | string | yes | Required. Project ID of the dataset request. |
List table ids in a BigQuery dataset. Supports pagination. Use page_size to limit results and page_token to retrieve next page.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| datasetId | string | yes | Required. Dataset ID of the table request. |
| pageSize | integer | no | Optional. The maximum number of results to return in a single response page. If unset, the default page size of 5000 is used. |
| pageToken | string | no | Optional. Page token, returned by a previous call, to request the next page of results. |
| projectId | string | yes | Required. Project ID of the table request. |
Get metadata information about a BigQuery table.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| datasetId | string | yes | Required. Dataset ID of the table request. |
| projectId | string | yes | Required. Project ID of the table request. |
| tableId | string | yes | Required. Table ID of the table request. |
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:/
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dryRun | boolean | no | Optional. If set to true, BigQuery doesn't run the job. Instead, if the query is valid, BigQuery returns statistics about the job such as how many bytes would be processed. If the query is invalid, an |
| labels | object | no | Optional. The labels associated with this query. Labels can be used to organize and group query jobs. Label keys and values can be no longer than 63 characters, can only contain lowercase letters, num |
| projectId | string | yes | Required. Project that will be used for query execution and billing. |
| query | string | yes | Required. The query to execute in the form of a GoogleSQL query. |
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 `
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dryRun | boolean | no | Optional. If set to true, BigQuery doesn't run the job. Instead, if the query is valid, BigQuery returns statistics about the job such as how many bytes would be processed. If the query is invalid, an |
| labels | object | no | Optional. The labels associated with this query. Labels can be used to organize and group query jobs. Label keys and values can be no longer than 63 characters, can only contain lowercase letters, num |
| projectId | string | yes | Required. Project that will be used for query execution and billing. |
| query | string | yes | Required. The query to execute in the form of a GoogleSQL query. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Google BigQuery or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
No release history has been published for this listing yet.
This listing has published no versions to the marketplace yet.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Google BigQuery can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.