Skip to content
Custom Connectors

Full read-write Claude connector for BigQuery

Let Claude run scoped reads and writes against your BigQuery data

Stop hand-running SQL to model and refresh tables. Claude queries your warehouse, materializes results into new tables, loads and appends rows, and runs table-replacing actions only once you approve them, all where your data already lives.

BigQuery is Google Cloud's serverless data warehouse, where many teams keep their analytics tables, event data, and reporting models. People want Claude to do more than read query results: to run jobs, write tables, and manage datasets on their behalf.

What is a BigQuery MCP server?

A BigQuery MCP server is a small hosted service that exposes BigQuery's data and actions to Claude over the Model Context Protocol, so Claude can records, tables, and queries inside your own account. We build it as a custom connector with separate read and write tools, and destructive actions stay gated behind your approval.

What can BigQuery's current connector do today?

Today, BigQuery's available Claude and MCP connections lean toward read and query: Claude can run SELECT queries and inspect schemas, but creating tables, loading data, and managing datasets are typically limited or out of scope. A custom BigQuery connector adds those write actions with scoped, confirmation-gated controls.

What does full read-write BigQuery access unlock?

Full read-write BigQuery access lets Claude create and replace tables, run write queries, load and append rows, materialize query results into new tables, and manage datasets, all within the permissions you grant. The modeling and data preparation that used to mean hand-running SQL happen where your warehouse already lives.

  • Run a CREATE TABLE AS SELECT to materialize a query result into a new table
  • Append rows to an existing table from a query or staged data
  • Create or update a dataset and set its default table expiration
  • Run an INSERT, UPDATE, or MERGE statement against a table after you approve it
  • Build a scheduled-query candidate and save the SQL for your review
  • Replace a reporting table in place once the refreshed query validates

Can Claude create and write to tables in BigQuery?

Yes. With a full read-write BigQuery connector, Claude can create and replace tables, run CREATE TABLE AS SELECT, and append rows within the datasets you grant. Default read-leaning connections focus on SELECT queries and schema inspection, so writing tables needs a purpose-built connector scoped to your warehouse.

Can Claude run an UPDATE or MERGE statement in BigQuery?

Claude can prepare an INSERT, UPDATE, or MERGE statement against a table and show you the SQL first. These are gated write tools, so the statement runs only after you approve it. Read tools like running queries and inspecting schemas flow freely, while modifying actions wait for your confirmation.

Can I limit which datasets and projects Claude can write to in BigQuery?

Yes. The connector authenticates with a service account or OAuth credential you control, so it inherits only the BigQuery permissions you grant. You can scope it to specific projects and datasets, separate read and write roles, and restrict access by IP range. It never has more access than the credential itself.

How a BigQuery connector works

We build a small MCP server that connects to BigQuery with a scoped service account or OAuth credential limited to the datasets the work needs. Read tools (run query, inspect schema) and write tools (create table, load, modify) are separated, and destructive or table-replacing actions require your confirmation. Claude only ever has the access the credential already has, and you can restrict it to specific projects, datasets, or IP ranges.

Frequently asked questions

Can Claude create and write to BigQuery tables, not just run SELECT queries?
Yes. A custom BigQuery connector exposes write tools, so Claude can run CREATE TABLE AS SELECT, load data, and append rows within the datasets you grant. Default read-leaning connections focus on queries and schema inspection, which is why creating and writing tables needs a purpose-built connector scoped to your warehouse.
Will Claude drop or overwrite a table without my approval?
No. Table-replacing and destructive actions like DROP, TRUNCATE, or write-disposition overwrites are separate, gated write tools. Claude can prepare the statement and show you the SQL, but it runs only after you approve it. You decide which actions are automatic and which require a confirmation step.
Can I limit which datasets and projects Claude can write to?
Yes. The connector authenticates with a service account or OAuth credential you control, so it inherits only the BigQuery permissions you grant. You can scope it to specific projects and datasets, separate read and write roles, and restrict access by IP range. It never has more access than the credential itself.

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.