RunPod

Provides an MCP server to manage RunPod pods, endpoints, templates, volumes, and authentications via MCP-compatible clients.

typescript

0

GitHub Stars

typescript

Language

6 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

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

You can interact with the RunPod REST API using an MCP-compatible client, such as Claude, through this RunPod MCP Server. It exposes practical controls to manage pods, endpoints, templates, network volumes, and container registry authentications, enabling you to automate and streamline RunPod operations from your MCP client.

How to use

Connect your MCP client to the RunPod MCP Server to manage RunPod resources from your preferred interface. You can list pods, create new pods, update pod details, start or stop pods, and remove pods. You can also create and manage serverless endpoints, define and modify templates, manage network volumes, and handle container registry authentications. Use the client commands to send the appropriate MCP requests for each resource type, and monitor responses to track state and details.

How to install

Follow these concrete steps to set up the RunPod MCP Server locally and connect it to your client.

Additional setup and configuration

Prerequisites include Node.js 18 or higher, a RunPod account with an API key, and an MCP-compatible client like Claude for Desktop.

Configuration and running

Set your RunPod API key in the environment where the MCP server runs so that it can authenticate with RunPod services.

Security considerations

Protect your RunPod API key and avoid exposing it in shared environments. Consider using a separate API key with restricted permissions for MCP access and ensure you only enable production-ready security measures in sensitive deployments.

Usage examples

Once connected, use your MCP client to issue commands that correspond to the actions you want on RunPod resources, such as listing pods, creating new pods with specific configurations, or managing endpoints and templates.

Troubleshooting and notes

If you encounter authentication errors, verify that RUNPOD_API_KEY is correctly set in the environment where the MCP server runs. Check network access to the RunPod API and ensure your API key has the necessary permissions for the requested operations.

Available tools

Pods management

Create, list, get details, update, start, stop, and delete pods to run experiments or workloads on RunPod infrastructure.

Endpoints management

Create, list, get details, update, and delete serverless endpoints to expose RunPod-based services.

Templates management

Create, list, get details, update, and delete templates used to standardize pod or endpoint configurations.

Network volumes management

Create, list, get details, update, and delete network volumes for persistent storage.

Container registry authentications management

Create, list, get details, and delete authentications for container registries accessed by pods.