Runpod MCP

The Runpod MCP server exposes Runpod's control plane as structured tool calls, so an MCP-capable agent can manage infrastructure without shelling out. It is the same Runpod REST API that runpodctl uses. Pick MCP when its tools are connected (typed params, structured errors, no shell quoting).

This skill does three things: it connects the server, routes each request to the journey skill that carries its procedure (Route by intent), and owns the answer contract below, which every reply follows.

For a multi-step job, read the worked example before calling tools. Tool calls are easy to issue and easy to issue in the wrong order. The verified end-to-end sequences live in runpod/golden-paths/README.md (image → template → endpoint, pod → volume → serverless, multi-region, autoscaling, monitoring). The journey skills cover procedure within one journey; the paths cover what order to do a whole job in.

Connect