How to integrate Google BigQuery MCP with Claude Code

Manage your Google BigQuery directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns. You can do this in two different ways: Via Composio Connect - Direct and easiest approach Via Composio SDK - Programmatic approach with more control

Google BigQuery logoGoogle BigQuery
Oauth2Google Service Account

Google BigQuery is a fully managed cloud data warehouse for fast SQL analytics on massive datasets. It's designed to help you analyze big data with ease, speed, and built-in machine learning.

63 Tools

Introduction

Manage your Google BigQuery directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.

You can do this in two different ways:

  1. Via Composio Connect - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Also integrate Google BigQuery with

Why use Composio?

  • Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
  • Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Handling Large tool responses out of LLM context to minimize context rot.
  • Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

Connecting Google BigQuery to Claude Code using Composio

1. Add the Composio MCP to Claude

Terminal

2. Start Claude Code

bash
claude

3. Open your MCP list

bash
/mcp

4. Select Composio and click on Authenticate

Select Composio and click Authenticate

5. This will redirect you to the Composio OAuth page. Complete the flow by authorizing Composio and you're all set.

Composio OAuth authorization page
Composio authorization complete
Ask Claude to connect to your account and authenticate via the link

What is the Google BigQuery MCP server, and what's possible with it?

The Google BigQuery MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Google BigQuery account. It provides structured and secure access to your data warehouse, so your agent can perform actions like running SQL queries, analyzing datasets, extracting insights, and automating reporting on your behalf.

  • Instant SQL query execution: Have your agent run complex analytical queries on any of your BigQuery datasets and get results in real time.
  • Custom data analysis and reporting: Instruct your agent to generate summaries, trends, or statistics by querying specific tables or views.
  • Automated data extraction: Let your agent fetch and transform data for integration with other tools or for further analysis.
  • Interactive business intelligence: Enable your agent to answer ad hoc data questions, visualize aggregated data, or pull specific metrics from massive datasets instantly.
  • Streamlined workflow automation: Use your agent to automate recurring BigQuery tasks, such as daily audits or data slice generation, without manual effort.

Connecting Google BigQuery via Composio SDK

Composio SDK is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here Google BigQuery) for even more tool search precision. It's secure and reliable.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step10 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Claude Pro, Max, or API billing enabled Anthropic account
  • Composio API Key
  • A Google BigQuery account
  • Basic knowledge of Python or TypeScript
2

Install Claude Code

bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To install Claude Code, use one of the following methods based on your operating system:

3

Set up Claude Code

bash
cd your-project-folder
claude

Open a terminal, go to your project folder, and start Claude Code:

  • Claude Code will open in your terminal
  • Follow the prompts to sign in with your Anthropic account
  • Complete the authentication flow
  • Once authenticated, you can start using Claude Code
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)
5

Install Composio library

npm install @composio/core dotenv

Install the Composio TypeScript library to create MCP sessions.

  • @composio/core provides the core Composio functionality
  • dotenv loads environment variables from your .env file
6

Generate Composio MCP URL

import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['googlebigquery'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http googlebigquery-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Create a script to generate a Composio MCP URL for Google BigQuery. This URL will be used to connect Claude Code to Google BigQuery.

What's happening

  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for Google BigQuery
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it
7

Run the script and copy the MCP URL

node --loader ts-node/esm generate_mcp_url.ts
# or if using tsx
tsx generate_mcp_url.ts

Run your TypeScript script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output
8

Add Google BigQuery MCP to Claude Code

bash
claude mcp add --transport http googlebigquery-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

In your terminal, add the MCP server using the command from the previous step. The command format is:

  • claude mcp add registers a new MCP server with Claude Code
  • --transport http specifies that this is an HTTP-based MCP server
  • The server name (googlebigquery-composio) is how you'll reference it
  • The URL points to your Composio Tool Router session
  • --headers includes your Composio API key for authentication

After running the command, close the current Claude Code session and start a new one for the changes to take effect.

9

Verify the installation

bash
claude mcp list

Check that your Google BigQuery MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your googlebigquery-composio entry in the list
  • This confirms that Claude Code can now access Google BigQuery tools

If everything is wired up, you should see your googlebigquery-composio entry listed:

Claude Code MCP list showing the toolkit MCP server
10

Authenticate Google BigQuery

The first time you try to use Google BigQuery tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with Google BigQuery
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the Google BigQuery authorization flow
  • Return to the terminal and start using Google BigQuery through Claude Code

Once authenticated, you can ask Claude Code to perform Google BigQuery operations in natural language. For example:

  • "Run yesterday's sales summary query"
  • "Find top 10 customers by revenue"
  • "Analyze traffic data for last quarter"

Complete Code

Here's the complete code to get you started with Google BigQuery and Claude Code:

import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['googlebigquery'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http googlebigquery-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Conclusion

You've successfully integrated Google BigQuery with Claude Code using Composio's MCP server. Now you can interact with Google BigQuery directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for Google BigQuery operations
  • Secure authentication through Composio's managed MCP
  • Tool Router for dynamic tool discovery and execution

Next steps:

  • Try asking Claude Code to perform various Google BigQuery operations
  • Add more toolkits to your Tool Router session for multi-app workflows
  • Integrate this setup into your development workflow for increased productivity

You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

TOOLS

Supported Tools

Every Google BigQuery action and event your agent gets out of the box.

Cancel BigQuery Job

Tool to cancel a running BigQuery job.

Create Capacity Commitment

Tool to create a new capacity commitment resource in BigQuery Reservation.

Create BigQuery Connection

Tool to create a new BigQuery connection to external data sources using the BigQuery Connection API.

Create Analytics Hub Data Exchange

Tool to create a new Analytics Hub data exchange for sharing BigQuery datasets.

Create Analytics Hub Listing

Tool to create a new listing in a BigQuery Analytics Hub data exchange.

Create BigQuery Dataset

Tool to create a new BigQuery dataset with explicit location, labels, and description using the BigQuery Datasets API.

Create Analytics Hub Listing

Tool to create a new listing in a data exchange using Analytics Hub API.

Create BigQuery Data Policy (v2beta1)

Tool to create a new data policy under a project with specified location using the v2beta1 BigQuery Data Policy API.

Create Analytics Hub Query Template

Tool to create a new query template in a BigQuery Analytics Hub Data Clean Room (DCR) data exchange.

Create BigQuery Reservation

Tool to create a new BigQuery reservation resource to guarantee compute capacity (slots) for query and pipeline jobs.

Create BigQuery Reservation Assignment

Tool to create a BigQuery reservation assignment that allows a project, folder, or organization to submit jobs using slots from a specified reservation.

Create BigQuery Routine

Tool to create a new user-defined routine (function or procedure) in a BigQuery dataset.

Create BigQuery Table

Tool to create a new, empty table in a BigQuery dataset.

Delete BigQuery Dataset

Tool to delete a BigQuery dataset specified by datasetId via the datasets.

Delete BigQuery Job Metadata

Tool to delete the metadata of a BigQuery job.

Delete BigQuery ML Model

Tool to delete a BigQuery ML model from a dataset.

Delete BigQuery Routine

Tool to delete a BigQuery routine by its ID.

Delete BigQuery Table

Tool to delete a BigQuery table from a dataset.

Get BigQuery ML Model

Tool to retrieve a specific BigQuery ML model resource by model ID.

Get BigQuery Connection IAM Policy

Tool to get the IAM access control policy for a BigQuery connection resource.

Get BigQuery Dataset Metadata

Tool to retrieve BigQuery dataset metadata including location via the datasets.

Get BigQuery Job

Tool to retrieve information about a specific BigQuery job.

Get BigQuery Query Results

Tool to get the results of a BigQuery query job via RPC.

Get BigQuery Routine

Tool to retrieve a BigQuery routine (user-defined function or stored procedure) by its ID.

Get BigQuery Routine IAM Policy

Tool to retrieve the IAM access control policy for a BigQuery routine resource.

Get BigQuery Service Account

Tool to get the service account for a project used for interactions with Google Cloud KMS.

Get BigQuery Table IAM Policy

Tool to retrieve the IAM access control policy for a BigQuery table resource.

Get BigQuery Table Schema

Tool to fetch a BigQuery table's schema and metadata without querying row data.

Insert Data into BigQuery Table

Tool to stream data into BigQuery one record at a time without running a load job.

Insert BigQuery Job

Tool to start a new asynchronous BigQuery job (query, load, extract, or copy).

Insert BigQuery Job with Upload

Tool to start a new BigQuery load job with file upload.

List Analytics Hub Listings

Tool to list all listings in a given Analytics Hub data exchange.

List BigQuery Connections

Tool to list BigQuery connections in a given project and location.

List BigQuery Capacity Commitments

Tool to list all capacity commitments for the admin project.

List Data Exchange Listings

Tool to list all listings in a given Analytics Hub data exchange using the v1beta1 API.

List BigQuery Datasets

Tool to list datasets in a specific BigQuery project, including dataset locations.

List BigQuery Jobs

Tool to list all jobs that you started in a BigQuery project.

List BigQuery Data Transfer Locations

Tool to list information about supported locations for BigQuery Data Transfer Service.

List Connections in Location

Tool to list BigQuery connections in a given project and location using the v1beta1 API.

List BigQuery Location Data Policies

Tool to list all data policies in a specified parent project and location using the v2beta1 API.

List BigQuery Models

Tool to list all BigQuery ML models in a specified dataset.

List Organization Data Exchanges

Tool to list all data exchanges from projects in a given organization and location using Analytics Hub API.

List BigQuery Projects

Tool to list BigQuery projects to which the user has been granted any project role.

List Analytics Hub Query Templates

Tool to list all query templates in a given Analytics Hub data exchange.

List BigQuery Reservation Assignments

Tool to list BigQuery reservation assignments.

List BigQuery Reservation Groups

Tool to list all BigQuery reservation groups for a project in a specified location.

List BigQuery Reservations

Tool to list all BigQuery reservations for a project in a specified location.

List BigQuery Routines

Tool to list all routines (user-defined functions and stored procedures) in a BigQuery dataset.

List BigQuery Row Access Policies

Tool to list all row access policies on a specified BigQuery table.

List BigQuery Table Data

Tool to list the content of a BigQuery table in rows via the REST API.

List BigQuery Tables

Tool to list tables in a BigQuery dataset via the REST API.

Patch BigQuery Dataset

Tool to update an existing BigQuery dataset using RFC5789 PATCH semantics.

Patch BigQuery ML Model

Tool to update specific fields in an existing BigQuery ML model using PATCH semantics.

Patch BigQuery Table

Tool to update specific fields in an existing BigQuery table using RFC5789 PATCH semantics.

Query

Query Tool runs a SQL query in BigQuery using the REST API.

Search All BigQuery Reservation Assignments

Tool to search all BigQuery reservation assignments for a specified resource in a particular region.

Set BigQuery Routine IAM Policy

Tool to set the IAM access control policy for a BigQuery routine resource.

Test BigQuery Routine IAM Permissions

Tool to test which IAM permissions the caller has on a BigQuery routine.

Undelete BigQuery Dataset

Tool to undelete a BigQuery dataset within the time travel window.

Update BigQuery Connection

Tool to update a specified BigQuery connection using the BigQuery Connection API.

Update BigQuery Dataset

Tool to update information in an existing BigQuery dataset using the PUT method.

Update BigQuery Routine

Tool to update an existing BigQuery routine (function or stored procedure).

Update BigQuery Table

Tool to update an existing BigQuery table.

FAQ

Frequently asked questions

With a standalone Google BigQuery MCP server, the agents and LLMs can only access a fixed set of Google BigQuery tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Google BigQuery and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Code fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Google BigQuery tools.

Yes, absolutely. You can configure which Google BigQuery scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Google BigQuery data and credentials are handled as safely as possible.

Start with Google BigQuery.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Google BigQuery tool your agent needs.Free to start.

Start building