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 owns the MCP side: it connects and authenticates the server, sets the tool-use rules, routes each request to the journey skill that carries its procedure (Route by intent), and owns the answer contract below, which every reply follows. Lane choice (MCP vs runpodctl vs flash) belongs to the router.

For a multi-step job, read the worked example before calling tools: tool calls are easy to issue in the wrong order. The golden paths (index) cover what order to do a whole job in; the journey skills cover procedure within one journey.

Connect