← Index

BigQuery Data Platform

io.github.deBilla/data-platform-mcpv0.1.2Databases

Read-only BigQuery tools for plain-language data questions, with a cost gate on every query

The current version, v0.1.2, was published to the official MCP registry on 2026-09-02. It is distributed as data-platform-mcp on PyPI, filed under Databases by this index, and declares 10 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.

In-path gate · all MCP tools

Using BigQuery Data Platform in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire
Trust verdict · v1 advisory · method
NOT YET SCREENEDno verdict on file

Verdict not yet evaluated for this tool. The semantic screen takes adversarial cases first; coverage rolls out as the corpus expands (15/150 labels to graduation). The deterministic conformance probe is built but has not yet run on the public corpus, so a recorded verdict here is REVIEW or UNVERIFIED, never a clearing ALLOW. Until a verdict is recorded, an agent should treat this tool as not-yet-cleared and fall back to its own checks. Method: the eval, four-state verdict, honest limits.

Own this server? Screen its description →

That verdict was true at screening time (snapshot 2026-09-02).

Contracts can change after screening, with no version bump. The gate pins BigQuery Data Platform’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Related: how to trust an MCP server · screen before install · silent contract drift

Environment variables
BQ_MCP_ENVIRONMENTS

JSON map of environment name to BigQuery settings (project, location, impersonate, dataset_allowlist, byte caps). Omit when using a config file at ~/.config/data-platform-mcp/config.toml.

BQ_MCP_DEFAULT_ENVIRONMENT

Environment used when a tool call omits the environment argument.

BQ_MCP_CONFIG

Path to a TOML config file, overriding ~/.config/data-platform-mcp/config.toml.

BQ_IMPERSONATE_SERVICE_ACCOUNT

Read-only service account to impersonate, making read-only a property of the identity rather than of this code. Create it with `data-platform-mcp setup`.

BQ_PROJECT

GCP project whose BigQuery datasets are queried. Falls back to the project associated with Application Default Credentials.

BQ_LOCATION

BigQuery location for jobs and datasets. Defaults to US.

BQ_DATASET_ALLOWLIST

Comma-separated dataset IDs the server may read. Empty means all datasets.

BQ_WARN_BYTES

Scan size above which a query is returned for user confirmation instead of run. Defaults to 1 GiB.

BQ_MAX_BYTES_BILLED

Hard per-query scan cap; a query estimated above this never runs. Defaults to 5 GiB.

BQ_MCP_AUDIT_LOG

Path for the JSONL tool-call audit log, or 'off' to disable it. SQL text is never recorded, only a hash and a length.

MCP quality score · maturity, not trust · methodology
freshness
25
completeness
15
installability
25
documentation
15
stability
5
Alternatives in Databases