Runpod MCP Ts MCP Server

MCP server for interacting with RunPod API

Local serverstdio

What is the Runpod MCP Ts MCP Server?

MCP server for interacting with RunPod API

What it actually does

This Model Context Protocol (MCP) server enables you to interact with the RunPod REST API through Claude or other MCP-compatible clients.

  • Pods — Create, list, get details, update, start, stop, and delete pods
  • Endpoints — Create, list, get details, update, and delete serverless endpoints
  • Templates — Create, list, get details, update, and delete templates
  • Network Volumes — Create, list, get details, update, and delete network volumes
  • Container Registry Authentications — Create, list, get details, and delete authentications

Configuration

  • Node.js 18 or higher - A RunPod account and API key - Claude for Desktop or another MCP-compatible client

More MCP options

Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.

Maintainer setup documentation.

How to install the Runpod MCP Ts MCP Server

{
  "mcpServers": {
    "runpod": {
      "command": "node",
      "args": [
        "/path/to/runpod-mcp-server/build/index.js"
      ],
      "env": {
        "RUNPOD_API_KEY": "YOUR_RUNPOD_API_KEY"
      }
    }
  }
}

From the project documentation. Replace placeholders and example paths before connecting.

Configuration

  • Node.js 18 or higher - A RunPod account and API key - Claude for Desktop or another MCP-compatible client
VariableDescriptionRequired
RUNPOD_API_KEYDeclared in the maintainer’s client configuration.Check documentation

Example prompts to try

  • “Use Runpod MCP Ts to Prerequisites.”
  • “Use Runpod MCP Ts to Installation.”
  • “Use Runpod MCP Ts to Configuration.”

Frequently asked questions

MCP server for interacting with RunPod API Confirm the tools offered by your installed version in the connected client. Tool availability and permissions depend on the server and account configuration.