BigQuery Data Platform MCP Server

What the code does

We read the source, 23 h ago · rules 995398eba69f

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

        return subprocess.call([bash, str(path), *args])

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

        return subprocess.call([bash, str(path), *args])

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add data-platform-mcp -- uvx data-platform-mcp

{
  "mcpServers": {
    "data-platform-mcp": {
      "command": "uvx",
      "args": [
        "data-platform-mcp"
      ]
    }
  }
}

[mcp_servers.data-platform-mcp]
command = "uvx"
args = ["data-platform-mcp"]

{
  "mcpServers": {
    "data-platform-mcp": {
      "command": "uvx",
      "args": [
        "data-platform-mcp"
      ]
    }
  }
}

{
  "servers": {
    "data-platform-mcp": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "data-platform-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: 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).