Mcp servers

Skill jpantsjoha/googlecloud-plugin/skills/mcp-servers

Configure, install, and maintain Google-managed and self-hosted MCP servers for GCP. Covers setup, auth (ADC and SA key), capability map, troubleshooting, and version tracking. Every MCP entry includes a gcloud CLI fallback. Use when the user mentions: MCP setup, google MCP, model context protocol GCP, MCP install, MCP auth, genai toolbox, MCP tools GCP, configure MCP.From its SKILL.md

Install

npx -y skills add jpantsjoha/googlecloud-plugin --skill mcp-servers

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

5.7 KB, as published. Nobody here has run it

MCP Servers — Google Cloud

Configure and maintain Model Context Protocol (MCP) servers for Google Cloud. All auth flows through ADC or explicit SA key path — no credential values stored anywhere.

Auth Architecture

All GCP MCP servers authenticate via Application Default Credentials (ADC):

# Authenticate locally (developer machine)
gcloud auth application-default login

# Authenticate for a service account (CI/CD or production agent)
gcloud auth activate-service-account --key-file=/path/to/sa-key.json
gcloud auth application-default login [email protected]

What the plugin ships vs what you opt into

The portable mcp.json (Agent Plugins 1.0.0) declares one server — gcloud — because that is the only one that starts with no user-supplied configuration:

{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/mcp.schema.json",
  "mcpServers": {
    "gcloud": { "type": "stdio", "command": "npx", "args": ["-y", "@google-cloud/gcloud-mcp"] }
  }
}

Two consequences worth knowing:

No env block. Agent Plugins expands only ${PLUGIN_ROOT} and ${PLUGIN_DATA}. A ${GCP_PROJECT_ID} placeholder would be passed through literally and mis-set your project. Export it in your own shell instead — the client passes the ambient environment through:
```
export CLOUDSDK_CORE_PROJECT=your-project-id
gcloud auth application-default login
```
The capability table below lists logical GCP capabilities, not entries in mcp.json. Most are reachable through the gcloud server; anything needing its own config file is an opt-in you add to your client's own MCP settings.

Google-Managed MCP Servers (v0.1)

Server	Capability	Required Role
`google-cloud-run`	Deploy/manage Cloud Run services	`roles/run.admin`
`google-bigquery`	Query/manage BigQuery datasets	`roles/bigquery.user`
`google-gke`	GKE cluster management	`roles/container.developer`
`google-storage`	Cloud Storage bucket ops	`roles/storage.objectAdmin`
`google-vertex-ai`	Vertex AI model/endpoint management	`roles/aiplatform.user`
`google-iam`	IAM policy management	`roles/iam.securityAdmin`
`google-logging`	Cloud Logging query/ingest	`roles/logging.viewer`
`google-monitoring`	Metrics, alerting	`roles/monitoring.viewer`

GenAI Toolbox (Google's MCP for Databases) — opt-in

Google's MCP Toolbox for Databases enables LLM agents to query Cloud SQL, AlloyDB, Spanner, BigQuery, and more safely.

Why this is not in mcp.json. Toolbox needs --config <your tools.yaml>, a path only you can supply. No Agent Plugins placeholder can express it, so shipping it in the portable manifest would mean a server that fails to start on every fresh install. Add it to your own client config once you have a tools.yaml. (A failing server is isolated by spec — it would not take the skills down — but a broken default is still a broken default.)

# Run the toolbox MCP server (requires a tools.yaml pointing at your database)
# Tested 2026-07-23: this is the correct package. Full docs: https://mcp-toolbox.dev
npx -y @toolbox-sdk/server --stdio --config tools.yaml

# Example tools.yaml (BigQuery source)
# sources:
#   my-bq:
#     kind: bigquery
#     project: PROJECT_ID
# tools:
#   run_query:
#     source: my-bq
#     description: Run a read-only BigQuery query
#     statement: SELECT ...

Package note (tested 2026-07-23): use @toolbox-sdk/server via npx — not pip install toolbox-core / uvx toolbox-core. toolbox-core is the Python SDK library for building apps; it has no server CLI entry point.

Self-Hosted / Community MCPs

Server	Install	Use
`gcloud-mcp`	`npx @modelcontextprotocol/server-gcloud`	Broad gcloud CLI coverage
`k8s-mcp`	Standard k8s MCP server	Kubernetes API for GKE

Troubleshooting

Symptom	Likely Cause	Fix
`401 Unauthorized`	ADC not set or expired	`gcloud auth application-default login`
`403 Permission Denied`	SA missing required role	Add role per table above
`MCP server not found`	Server not installed	Check install step in references/
Connection timeout	VPC firewall blocking	Verify Private Google Access + firewall