GCP Platform Engineer MCP server
io.github.deBilla/platform-mcp·v0.4.0·2 starsRead-only GCP tools for debugging incidents and finding cost savings
2 stars31 downloads/wk
Reviews
Write oneNobody has reviewed GCP Platform Engineer yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
GCP Platform Engineer tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-29 · same rubric, same numbers if you re-run it
- Code scan20 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 7 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How GCP Platform Engineer compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 92/100
- higher than 95% of 48,255 servers
- GitHub stars
- 2
- more than 75% of 28,688 servers
- Downloads a week
- 31
- more than 19% of 12,191 servers with a package
Install GCP Platform Engineer in Claude Code, Cursor or VS Code
claude mcp add platform-mcp -- uvx platform-mcp
What the publisher says
From the GCP Platform Engineer repository's README, as published. We do not edit it. Read it on GitHub
platform-mcp
<!-- Identifier for the official MCP registry; must match server.json. --> mcp-name: io.github.deBilla/platform-mcp
A read-only Model Context Protocol server that turns an AI agent (Claude Code, Claude Desktop, or any MCP client) into a GCP platform engineer. Point it at your Google Cloud projects and ask it to investigate incidents, take inventory, and surface cost-optimization opportunities — all without any ability to change your infrastructure.
Observation only. No tool in this server mutates state. Combined with a viewer-only identity (below), that gives you a hard, defense-in-depth guarantee that an agent can look but never touch.
What it can do
Typical prompts once it's connected:
- "What are the top error groups in the last 24 hours, and which one is newest?"
- "Which GKE node pools are over-provisioned? Show mean CPU against machine type."
- "Where can I reduce spend in this project?"
Multiple environments
One server can reach several projects. Define them under PLATFORMMCPENVIRONMENTS (see Configuration) and the agent picks one from the wording of your prompt:
- "Any errors in staging in the last hour?"
- "Compare Cloud Run services between staging and prod."
Every tool takes an optional environment argument. Omit it and the default environment is used; pass environment="production" to target another. Names, any aliases you define, common shorthands (prod, stg, qa, …) and bare project ids all resolve. An unrecognized name is an error listing the valid options — a typo can never silently retarget the wrong project.
Each environment carries its own service account, so staging and production are reached through separate identities from the same process, and every result echoes back the environment and project it came from.
Requirements
- Python 3.11+
- A Google Cloud project and credentials (your own login, or a service account)
- The gcloud CLI for the one-time setup
Install
uvx platform-mcp # no install step; uv fetches it on demand
pipx install platform-mcp # or keep it on PATHFrom a checkout, for development:
git clone https://github.com/deBilla/platform-mcp.git
cd platform-mcp
python3 -m venv .venv
./.venv/bin/pip install -e ".[dev]"Check your setup
platform-mcp doctorThis checks, for every configured environment, that Application Default Credentials exist, that the read-only service account can be impersonated, that a real API read succeeds, and that the billing export is readable — printing the exact command to fix whatever fails. Run it before reporting a problem.
One-time GCP setup
Run these once per project you want to reach — staging and production each need their own APIs enabled and their own read-only service account.
1. Enable the APIs the tools depend on:
gcloud services enable \
logging.googleapis.com monitoring.googleapis.com clouderrorreporting.googleapis.com \
recommender.googleapis.com cloudasset.googleapis.com cloudbilling.googleapis.com \
bigquery.googleapis.com \
--project YOUR_PROJECT_ID2. Grant read-only access to the identity the server runs as.
For local development with your own login (Application Default Credentials):
gcloud auth application-default loginShortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
GCP Platform Engineer: common questions
- Is GCP Platform Engineer MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the GCP Platform Engineer safety report
- How do I install GCP Platform Engineer?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does GCP Platform Engineer need an API key?
- No secret keys are declared. It reads 4 settings from the environment.
- Is GCP Platform Engineer maintained?
- The last commit was 13 days ago (2026-10-21). The latest release is v0.4.0.
- How does GCP Platform Engineer compare with other MCP servers?
- safety score 92/100 (higher than 95% of 48,255 servers); github stars 2 (more than 75% of 28,688 servers); downloads a week 31 (more than 19% of 12,191 servers with a package). Full comparison.