Runpod MCP Ts MCP Server

MCP server for interacting with RunPod API. The runpod mcp ts mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 3 defined tools rather than through you.

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

Its toolset

Everything the assistant can do here goes through one of these:

• Prerequisites — The Prerequisites tool exposed by this server
• Installation — 1. Clone the repository 2. Install dependencies: npm install 3. Build the server: npm run build
• Configuration — The Configuration tool exposed by this server

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at @smithery/cli on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Configuration

You will need one environment variable: RUNPOD_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

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

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Runpod MCP Ts's toolset — Prerequisites, Installation, Configuration — is a fair guide to whether it matches your workflow. It is maintained by antonioevans; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the runpod mcp ts mcp server does with a few real requests.