io.github.deBilla/platform-mcp is an MCP server that read-only GCP tools for debugging incidents and finding cost savings. Its tool list has not been published yet over stdio and sse, requires no API key, and scores 58/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"io-github-debilla-platform-mcp": {
"args": [
"platform-mcp"
],
"command": "uvx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Read-only GCP tools for debugging incidents and finding cost savings
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked platform-mcp against OSV.dev.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in cloud
Gives AI development tools Firebase-specific capabilities and expertise.
Cloud-powered AI platform with multi-agent swarms, sandboxes, and workflow automation
Draw cloud architecture diagrams with official AWS, Azure and GCP icons from a prompt or Terraform.
MCP Server for kubernetes management commands
MCP Security Weekly
Get CVE alerts and security updates for io.github.deBilla/platform-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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.
| Area | Tools |
|---|---|
| Environments | list_environments |
| Logs & errors | query_logs, get_recent_errors, list_error_groups |
| Metrics & alerting | query_metric, list_alert_policies, list_uptime_checks |
| Cost & recommendations | get_cost_breakdown, get_billing_info, list_cost_recommendations, list_recommendations |
| Resource inventory | search_assets, list_compute_instances, list_cloud_run_services, list_gke_clusters, list_sql_instances |
Typical prompts once it's connected:
One server can reach several projects. Define them under
PLATFORM_MCP_ENVIRONMENTS (see Configuration) and the agent
picks one from the wording of your prompt:
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.
gcloud CLI for the one-time setupuvx platform-mcp # no install step; uv fetches it on demand
pipx install platform-mcp # or keep it on PATH
From 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]"
platform-mcp doctor
This 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.
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_ID
2. 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 login
The identity needs these viewer rol