Google BigQuery

Live

OAUTH 2.0

DATA WAREHOUSE

Every dataset, table, and analytical query your team runs lives in Google BigQuery. Google BigQuery MCP gives your agent user-level authenticated access to your data warehouse scoped to the user who authorized it.

  • Acts as the user: Access and write actions stay tied to the Google BigQuery account that authorized the agent.
  • Credentials stay vaulted: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: User permissions enforced. 90-day audit trail.
Google BigQuery
agent · Acme Q3
Run
Run a query for daily active users over the last 30 days grouped by product tier.
S
gbq_query_run
0.9s
Analytics agent
Query ran in 0.9s, scanned 6.2 GB. Enterprise tier: 3,840 DAU avg; Pro: 12,200; Starter: 28,400. Enterprise up 12% vs prior 30d.
Sources: events.daily_active_users, 30 days
googlebigquerymcp
1 query
18:29
Message Claude...

Tools your analytics agent reaches for on Google BigQuery, scoped per user.

CALL ANY TOOL
List datasets and tables, inspect schemas, run SQL queries with user-level IAM, and monitor jobs.
gbq_datasets_list
List datasets
List all datasets in a GCP project the user has access to.
Parameters
Name
Type
Required
Description
project_id
string
Required
GCP project ID
gbq_tables_list
List tables
gbq_table_schema
Get table schema
gbq_query_run
Run query
gbq_job_get
Get job status
Build your Agent
Drop the toolkit in, point it at the user, and your analytics agent can use Google BigQuery from the first run.
import { ScalekitClient } from "@scalekit-sdk/node";
import { DynamicStructuredTool } from "@langchain/core/tools";
import { createReactAgent } from "@langchain/langgraph/prebuilt";
import { z } from "zod";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["googlebigquery"], toolNames: ["gbq_datasets_list", "gbq_tables_list", "gbq_table_schema"] },
pageSize: 100,
});

const lcTools = tools.map((t) => new DynamicStructuredTool({
name: t.tool.definition.name,
description: t.tool.definition.description,
schema: z.object({}).passthrough(),
func: async (args) => {
const { data } = await sk.tools.executeTool({
toolName: t.tool.definition.name,
identifier: "user_123",
params: args,
});
return JSON.stringify(data);
},
}));

const agent = createReactAgent({ llm, tools: lcTools });
import { ScalekitClient } from "@scalekit-sdk/node";
import OpenAI from "openai";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["googlebigquery"], toolNames: ["gbq_datasets_list", "gbq_tables_list", "gbq_table_schema"] },
pageSize: 100,
});

const llmTools = tools.map((t) => ({
type: "function",
function: {
name: t.tool.definition.name,
description: t.tool.definition.description,
parameters: t.tool.definition.input_schema,
},
}));

const resp = await openai.responses.create({
model: "gpt-4o", input: prompt, tools: llmTools,
});
import { ScalekitClient } from "@scalekit-sdk/node";
import Anthropic from "@anthropic-ai/sdk";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["googlebigquery"], toolNames: ["gbq_datasets_list", "gbq_tables_list", "gbq_table_schema"] },
pageSize: 100,
});

const llmTools = tools.map((t) => ({
name: t.tool.definition.name,
description: t.tool.definition.description,
input_schema: t.tool.definition.input_schema,
}));

const msg = await anthropic.messages.create({
model: "claude-sonnet-4-6", max_tokens: 1024,
tools: llmTools,
messages: [{ role: "user", content: prompt }],
});
import { Agent } from "@google/adk/agents";
import {
MCPToolset, StreamableHTTPConnectionParams,
} from "@google/adk/tools/mcp";

const toolset = new MCPToolset({
connectionParams: new StreamableHTTPConnectionParams({
url: "https://mcp.scalekit.com/googlebigquery",
headers: { Authorization: `Bearer ${userScopedToken}` },
}),
});

const agent = new Agent({
name: "agent", model: "gemini-2.0-flash",
tools: await toolset.getTools(),
});
Try these prompts
Paste any prompt into your agent to start using Google BigQuery.
Schema & discovery
Copy the prompt
Copied
List all datasets in [project].
Copy the prompt
Copied
Show the schema of [dataset.table].
Copy the prompt
Copied
Which tables are in [dataset]?
Copy the prompt
Copied
What views exist in [dataset]?
Query & analysis
Copy the prompt
Copied
Run: SELECT DATE(event_time), COUNT(*) FROM events GROUP BY 1.
Copy the prompt
Copied
Top 10 customers by revenue this quarter.
Copy the prompt
Copied
DAU by tier for the last 30 days.
Copy the prompt
Copied
Churn cohort analysis for Q3.
Monitoring & cost
Copy the prompt
Copied
Which queries scanned the most data today?
Copy the prompt
Copied
Job status for [job_id].
Copy the prompt
Copied
Estimated cost for query: [SQL].
Copy the prompt
Copied
Slowest queries in the last 6 hours.
SEE HOW AUTH WORKS
Users authorize Google BigQuery once. Their credentials stay vaulted, every call is checked, and every action is logged.
1
Authorize
Your user connects
Google BigQuery
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Google BigQuery
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Google BigQuery
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Google BigQuery
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
Same per-user auth pattern across other analytics agents and MCP connectors. Working code, live demos, fork what fits.
GTM
HubSpot to Slack updates agent
Watch HubSpot deal stage changes and post structured updates to the right Slack channel. Reps stop checking the CRM all day.
ENGINEERING
Engineering standup agent
Aggregate GitHub and GitLab activity, link to Jira, and post a daily standup digest to Slack. No async updates.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
Other connector libraries treat auth as a demo afterthought. Scalekit starts with user identity, scope enforcement, and audit.
01.
Shared tokens break per-user analytics
A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential so attribution, audit, and scope stay accurate.
// shared token
 audit → bot_service_account
 user_filter → broken

 // scalekit
 audit → user_abc
 scope → enforced ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
Google BigQuery today. Others tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions

Does the agent access Google BigQuery as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Google BigQuery oauth 2.0 stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Google BigQuery?
Yes. Pass a tool name filter to listScopedTools so the analytics agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Google BigQuery.

What happens when a user revokes Google BigQuery access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Does the agent inherit the user's BigQuery IAM roles?
Yes. Every query runs with the authorizing user's permissions. IAM roles, column-level security, and row-level access policies all apply. The agent cannot query data the user's account cannot reach.

Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""googlebigquery"": {
""url"": ""https://mcp.scalekit.com/googlebigquery"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.googlebigquery]
url = ""https://mcp.scalekit.com/googlebigquery""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""googlebigquery"": {
""url"": ""https://mcp.scalekit.com/googlebigquery"",
""type"": ""http""
}
}
}