GCP Platform Engineer runs on your own machine — the client starts it, so there is no endpoint to ping. 111 installs a week from pypi. Last commit 23 Sep 2026.
Read-only GCP tools for debugging incidents and finding cost savings
We read the source, 2 d ago · rules ccca72095570
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.
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch GCP Platform Engineer and you get told the day something new turns up.
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 platform-mcp -- uvx platform-mcp
{
"mcpServers": {
"platform-mcp": {
"args": [
"platform-mcp"
],
"command": "uvx"
}
}
}
[mcp_servers.platform-mcp]
command = "uvx"
args = ["platform-mcp"]
{
"mcpServers": {
"platform-mcp": {
"args": [
"platform-mcp"
],
"command": "uvx"
}
}
}
{
"mcpServers": {
"platform-mcp": {
"args": [
"platform-mcp"
],
"command": "uvx"
}
}
}
This one needs environment variables set before it will start:
PLATFORM_MCP_ENVIRONMENTS (JSON map of environment name to GCP settings. Omit when using a config file at ~/.config/platform-mcp/config.toml.), PLATFORM_MCP_DEFAULT_ENVIRONMENT (Environment used when a tool call omits the environment argument.), PLATFORM_MCP_CONFIG (Path to a TOML config file, overriding ~/.config/platform-mcp/config.toml.), PLATFORM_MCP_AUDIT_LOG (Path for the JSONL tool-call audit log, or 'off' to disable it.).
The author declared them in the registry entry; get the values from the project itself.
Read-only VMware incident correlation: timeline, spikes, root-cause routing. 2 MCP tools.
GSA Per Diem access readiness, lodging, and meals and incidental expense rates. 7 tools.
Connect AI coding tools to LogClaw incidents, logs, and anomaly detections.
Read-only MCP for OpenVibeCoding runs, workflows, proof, queue, replay, and incident reads.
MCP server for Rootly — incidents, alerts, escalations, and post-incident reports.
MCP server for Rootly — incidents, alerts, escalations, and post-incident reports.
Read-only MCP server for coding-agent traces, alerts, costs, usage, and budget health.
MCP server for Runframe incident management covering incidents, on-call, postmortems, and more.
Answers built from our own checks of this server.