BigQuery Data Platform MCP Server

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

Local serverstdio

What is the BigQuery Data Platform MCP Server?

BigQuery Data Platform is an MCP integration. Read-only BigQuery tools for plain-language data questions, with a cost gate on every query.

Packages and local setup

The published pypi package is data-platform-mcp, version 0.4.0. Its declared MCP transport is stdio.

The package declares 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_CODE_ASSET_LOCATION: Region holding BigQuery Studio notebooks and saved queries. Separate from BQ_LOCATION and usually different: code assets are regional and Dataform rejects multi-regions, so datasets in US typically pair with code assets in a region like us-central1. A wrong region returns an empty list rather than an error. Defaults to BQ_LOCATION.; 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..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.4.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related databases MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
BQ_MCP_ENVIRONMENTSJSON 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.Optional
BQ_MCP_DEFAULT_ENVIRONMENTEnvironment used when a tool call omits the environment argument.Optional
BQ_MCP_CONFIGPath to a TOML config file, overriding ~/.config/data-platform-mcp/config.toml.Optional
BQ_IMPERSONATE_SERVICE_ACCOUNTRead-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.Optional
BQ_PROJECTGCP project whose BigQuery datasets are queried. Falls back to the project associated with Application Default Credentials.Optional
BQ_LOCATIONBigQuery location for jobs and datasets. Defaults to US.Optional
BQ_CODE_ASSET_LOCATIONRegion holding BigQuery Studio notebooks and saved queries. Separate from BQ_LOCATION and usually different: code assets are regional and Dataform rejects multi-regions, so datasets in US typically pair with code assets in a region like us-central1. A wrong region returns an empty list rather than an error. Defaults to BQ_LOCATION.Optional
BQ_DATASET_ALLOWLISTComma-separated dataset IDs the server may read. Empty means all datasets.Optional
BQ_WARN_BYTESScan size above which a query is returned for user confirmation instead of run. Defaults to 1 GiB.Optional
BQ_MAX_BYTES_BILLEDHard per-query scan cap; a query estimated above this never runs. Defaults to 5 GiB.Optional
BQ_MCP_AUDIT_LOGPath for the JSONL tool-call audit log, or 'off' to disable it. SQL text is never recorded, only a hash and a length.Optional