Google Cloud MCP server

Last verified: 2026-09

Call selected GCP APIs.

Community Cloud & infra Needs a secret Claude Desktop, Cursor, Windsurf, Claude Code

What it does

This listing maps to Google's MCP Toolbox for Databases (googleapis/genai-toolbox) — SQL sources and prebuilt tools — not a full GCP admin MCP. If you wanted GCE/GKE control, that is a different Microsoft/Google server.

It sits in Cloud & infra: Most of these are admin APIs.

Good for

Connect MCP Toolbox to one database source and list_tables.
execute_sql with a service account that can only query that source.
Use prebuilt tools, not a guessed 'GCE create VM' tool — this package is not GCP admin.
Prefer the BigQuery server if the only source is BigQuery.

Tools

list_tables / execute_sql — Prebuilt database tools when a source is configured.
custom toolsets — Defined in the Toolbox config, not guessed.

Config (Claude Desktop / Cursor / Windsurf)

Paste the JSON below. Same mcpServers shape. Replace placeholder paths and secrets. Windows paths look like C:\\Users\\you\\project, not /path/to. Host-side steps →

Claude Desktop

OS	Config file
macOS	`~/Library/Application Support/Claude/claude_desktop_config.json`
Windows	`%APPDATA%\Claude\claude_desktop_config.json` (usually `C:\Users\<you>\AppData\Roaming\Claude\`)
Linux	`~/.config/Claude/claude_desktop_config.json`

Cursor

Scope	macOS / Linux	Windows
This project	`.cursor/mcp.json` in the repo root
This user	`~/.cursor/mcp.json`	`%USERPROFILE%\.cursor\mcp.json`

Windsurf

OS	Config file
macOS / Linux	`~/.codeium/windsurf/mcp_config.json`
Windows	`%USERPROFILE%\.codeium\windsurf\mcp_config.json`

{
  "mcpServers": {
    "gcp": {
      "command": "npx",
      "args": [
        "-y",
        "gcp-mcp"
      ],
      "env": {
        "GOOGLE_APPLICATION_CREDENTIALS": "/path/to/sa.json"
      }
    }
  }
}

Windsurf remote MCP: use serverUrl instead of url if the block below is HTTP.

One-liner: npx -y gcp-mcp

Secrets it wants: GOOGLE_APPLICATION_CREDENTIALS

Source repo →

How to get started

Read the Toolbox quick start. Configure one database source.
Use ADC or a service account that can only query that source.
If you needed cloud admin, stop — this package is not that.

Access risk

execute_sql is the database. A mis-labeled install that people think is 'GCP admin' is the other risk.

When to skip it

Skip it for BigQuery's dedicated server, or for AWS/Azure admin.

Instead: BigQuery, PostgreSQL, AWS.

Databases & dataBigQueryQuery Google BigQuery datasets. OfficialPostgreSQLRun SQL against a Postgres database. Cloud & infraAWSCall AWS APIs with the default credential chain.

Vs alternatives

Server	Official?	Needs a secret?	Best for
Google Cloud	No	Yes	Call selected GCP APIs.
BigQuery	No	Yes	Query Google BigQuery datasets.
PostgreSQL	Yes	Yes	Run SQL against a Postgres database.
AWS	No	Yes	Call AWS APIs with the default credential chain.

More in Cloud & infra

OfficialAWS Knowledge BaseQuery an Amazon Bedrock knowledge base. Cloud & infraAWSCall AWS APIs with the default credential chain. Cloud & infraAzureAzure Resource Manager via MCP. Cloud & infraCloudflareWorkers, KV, R2, and DNS via Cloudflare.

All 15 in this category →

FAQ

I wanted GCE/GKE control?

Wrong package. googleapis/genai-toolbox is SQL sources and toolsets. Azure/AWS pages on this site have the same 'index vs one server' issue.

What identity?

ADC or GOOGLE_APPLICATION_CREDENTIALS. execute_sql is the database.

Toolbox or BigQuery MCP?

BigQuery server if that is the warehouse. Toolbox if you are wiring several DB sources with custom toolsets.

Official Google?

Yes — MCP Toolbox for Databases.