Skip to main content
Glama
RunPod MCP Server

RunPod MCP Server

by Niel-RunPod

RunPod MCP Server

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

Features

The server provides tools for managing:

  • 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

Related MCP server: RunPod MCP Server

Setup

Prerequisites

  • Node.js 18 or higher

  • A RunPod account and API key

  • Claude for Desktop or another MCP-compatible client

Installing via Smithery

To install runpod-mcp-ts for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @runpod/runpod-mcp-ts --client claude

Installation

  1. Clone the repository

  2. Install dependencies:

    npm install
  3. Build the server:

    npm run build

Configuration

Set your RunPod API key as an environment variable:

# Linux/macOS
export RUNPOD_API_KEY=your_api_key_here

# Windows (Command Prompt)
set RUNPOD_API_KEY=your_api_key_here

# Windows (PowerShell)
$env:RUNPOD_API_KEY="your_api_key_here"

You can get your API key from the RunPod console.

Running the Server

Start the server:

npm start

Setting up with Claude for Desktop

  1. Open Claude for Desktop

  2. Edit the config file: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows)

  3. Add the server configuration:

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

Make sure to replace the "args": ["/path/to/runpod-mcp-server/build/index.js"] with the path to the build folder in the repository.

  1. Restart Claude for Desktop

Usage Examples

Here are some examples of how to use the server with Claude:

List all pods

Can you list all my RunPod pods?

Create a new pod

Create a new RunPod pod with the following specifications:
- Name: test-pod
- Image: runpod/pytorch:2.1.0-py3.10-cuda11.8.0-devel-ubuntu22.04
- GPU Type: NVIDIA GeForce RTX 4090
- GPU Count: 1

Create a serverless endpoint

Create a RunPod serverless endpoint with the following configuration:
- Name: my-endpoint
- Template ID: 30zmvf89kd
- Minimum workers: 0
- Maximum workers: 3

Security Considerations

This server requires your RunPod API key, which grants full access to your RunPod account. For security:

  • Never share your API key

  • Be cautious about what operations you perform

  • Consider setting up a separate API key with limited permissions

  • Don't use this in a production environment without proper security measures

License

MIT

Available Tools

26 tools
create-container-registry-authD

Inputs: name (required), password (required), username (required).

create-endpointD

Inputs: templateId (required), name, gpuCount, gpuTypeIds, +4 more.

create-network-volumeD

Inputs: name (required), size (required), dataCenterId (required).

create-podD

Inputs: imageName (required), env, name, ports, +7 more.

create-templateD

Inputs: name (required), imageName (required), env, ports, +7 more.

delete-container-registry-authD

Inputs: containerRegistryAuthId (required).

delete-endpointD

Inputs: endpointId (required).

delete-network-volumeD

Inputs: networkVolumeId (required).

delete-podD

Inputs: podId (required).

delete-templateD

Inputs: templateId (required).

get-container-registry-authD

Inputs: containerRegistryAuthId (required).

get-endpointD

Inputs: endpointId (required), includeWorkers, includeTemplate.

get-network-volumeD

Inputs: networkVolumeId (required).

get-podD

Inputs: podId (required), includeMachine, includeNetworkVolume.

get-templateD

Inputs: templateId (required).

list-container-registry-authsD

Inputs: no named parameters.

list-endpointsD

Inputs: includeWorkers, includeTemplate.

list-network-volumesD

Inputs: no named parameters.

list-podsD

Inputs: name, gpuTypeId, computeType, dataCenterId, +2 more.

list-templatesD

Inputs: no named parameters.

start-podD

Inputs: podId (required).

stop-podD

Inputs: podId (required).

update-endpointD

Inputs: endpointId (required), name, scalerType, workersMax, +3 more.

update-network-volumeD

Inputs: networkVolumeId (required), name, size.

update-podD

Inputs: podId (required), env, name, ports, +4 more.

update-templateD

Inputs: templateId (required), env, name, ports, +2 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    D1.9/5.0

    Scored across 26 tools

    Disambiguation5/5

    All 26 tools have distinct names combining a unique action verb and resource noun, making each tool clearly differentiated from the others without any overlap.

    Naming Consistency5/5

    Every tool follows the consistent verb_noun pattern in snake_case, using appropriate verbs like create, delete, get, list, start, stop, and update with the same set of resource nouns.

    Tool Count2/5

    With 26 tools, the server exceeds the recommended range of 3-15 for a well-scoped set. The number feels heavy for managing five resource types, though the operations are systematic.

    Completeness4/5

    Most resources have full CRUD coverage plus start/stop for pods. The only missing operation is update for container-registry-auth, but overall the tool surface covers the core lifecycle actions well.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that integrates Claude with the Terraform Cloud API, allowing Claude to manage your Terraform infrastructure through natural conversation.
      62
      23
      MIT
    • A
      license
      C
      quality
      A
      maintenance
      This Model Context Protocol server enables interaction with RunPod's REST API through Claude or other MCP-compatible clients, providing tools for managing pods, endpoints, templates, network volumes, and container registry authentications.
      36
      6,573 npm
      87
      Apache 2.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that allows integration with Claude Desktop by creating and managing custom tools that can be executed through the MCP framework.
      71 npm
      -
    • F
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server implementation that can be run directly or through Docker, enabling AI assistants to interact with external systems through the MCP standard.
      2
      -