Runpod MCP Ts

MCP开发工具

提供方 runpod · 包名 @smithery/cli

开发工具 stdio · 本地进程 无需鉴权 社区 / 第三方 Claude DesktopClaudeCursorWindsurf
查看接入方式

Runpod MCP服务器是一个用于通过MCP兼容客户端管理Runpod基础设施的工具,支持Pods、Serverless端点、模板、网络卷和容器注册表认证的管理。

一句话选型结论

按资料字段整理

Runpod MCP Ts 属于开发工具类 MCP 服务器,stdio · 本地进程,无需鉴权,可直接接入 Claude Desktop、Claude、Cursor 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式stdio · 本地进程 鉴权无需鉴权 部署方式本地部署
GitHub 星标 55 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

基础设施管理TypeScript本地部署云服务工具开发工具MCP协议Runpod

安装与配置

stdio · 本地进程 无需鉴权
客户端在本机拉起子进程,数据不出本机
npx -y @smithery/cli install @runpod/runpod-mcp-ts --client claude

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。
  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Runpod MCP Ts当前 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方runpod上游标注的维护方 runpod
分类开发工具本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式无需鉴权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时@smithery/cli · Node.js本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

10.5 KB
来自项目仓库与上游目录的原文,未做删改

Runpod MCP server

The official Runpod Model Context Protocol (MCP) server. It lets MCP clients such as Claude Code, Claude Desktop, Cursor, Windsurf, VS Code, opencode, and Pi manage your Runpod Pods, Serverless endpoints, templates, network volumes, and more.

We host it for you at https://mcp.runpod.io/ — point your client at that URL and sign in with Runpod. Nothing to install, no API key on disk. Or run it locally from npm as @runpod/mcp-server.

Quick start

The guided installer detects the clients you have installed, asks which to configure, and writes the config for you:```bash
npx @runpod/mcp-server@latest add


It offers two connection modes:

- **Hosted (recommended)** — points the client at the hosted server and authenticates with "Sign in with Runpod" (OAuth). No API key is stored on disk.
- **Local** — runs the server through `npx` and stores a `RUNPOD_API_KEY` in the client's config.

To undo later:```bash
npx @runpod/mcp-server@latest remove

To skip the prompts (from a script, CI, or a coding agent's shell), name the clients. Supported ids are claude-code, cursor, windsurf, claude-desktop, vscode, opencode, and pi:```bash
npx @runpod/mcp-server@latest add --client opencode,pi # hosted, sign in with Runpod
npx @runpod/mcp-server@latest add --client cursor --local # local, key read from RUNPOD_API_KEY
npx @runpod/mcp-server@latest remove --client opencode
npx @runpod/mcp-server@latest add --list # what's detected, and where each config lives


Without `--client` and without a terminal, the installer exits with code 2 and configures nothing. With flags it exits 0 when every client was configured and 1 when one failed.

### Or install the whole Runpod plugin

For the full agent setup, the official plugin marketplace bundles this server with a router skill plus five more — `runpod-mcp`, `runpodctl`, `flash`, `runpod-usage`, and `companion-clis`:```bash
npx skills add runpod/runpod-plugins-official

That works in Claude Code, Codex, Cursor, Copilot, Windsurf, Cline, Gemini, opencode, and 17+ other agents, and installs the skills — pair it with npx @runpod/mcp-server@latest add above for the control-plane tools.

In Claude Code, the native plugin route also wires up the hosted MCP server for you (OAuth included), so no separate setup is needed:```
/plugin marketplace add runpod/runpod-plugins-official
/plugin install runpod@runpod


### Requirements

- Node.js 20 or higher.
- A Runpod account and API key.

## Connect to the hosted server

To configure a client by hand, point it at the hosted server over HTTP (no local process, no API key stored).

**Claude Code:**```bash
claude mcp add --transport http runpod -s user https://mcp.runpod.io/

Other clients (Cursor, VS Code, Claude Desktop connectors, …) — use a URL-based MCP entry:```json
{
"mcpServers": {
"runpod": {
"url": "https://mcp.runpod.io/"
}
}
}


An OAuth-capable client starts the "Sign in with Runpod" flow automatically on first connect: it opens a browser, you log in to the Runpod console and approve, and the server obtains a Runpod API key scoped to your session. Nothing is stored on disk.

> **Which account does OAuth pick?** The key is minted for whichever account or team profile your browser's console session has selected when you approve. If you belong to multiple teams, switch to the right profile in the console first (or check afterwards — the resources the tools return are that profile's). To change it later, switch profiles in the console and re-authenticate from your MCP client.

> Prefer your own API key over OAuth? Append `--header "Authorization: Bearer YOUR_API_KEY"` to the `claude mcp add` command (or add a `headers` block in the JSON). The server forwards that key to the Runpod API directly.

### If sign-in fails with HTTP 403

A `403 Forbidden` response with the header `X-Vercel-Mitigated: deny` means the hosted server's firewall has temporarily blocked your IP address, usually after a burst of unauthenticated requests from an MCP client. This happens most often with Codex, which sends many unauthenticated requests while it signs in. The block covers every path, including `/register` and requests that carry an API key, and lifts on its own within an hour. Wait for it to expire, then use one of these options so the next connection doesn't trip it again.

You can send your API key as a header instead of signing in with OAuth, as described above. Authenticated requests don't count toward the limit. In Codex, add the key to the server entry in `~/.codex/config.toml`:```toml
[mcp_servers.runpod]
url = "https://mcp.runpod.io/"
bearer_token_env_var = "RUNPOD_API_KEY"

Then export RUNPOD_API_KEY in the shell that launches Codex.

You can also run the server locally. The local server calls the Runpod API directly, so the hosted firewall only affects its search-docs tool, which still searches through the hosted server.

Usage analytics

The hosted server records one anonymous event per tool call (tool name, status, duration, transport) and per guide resource read (guide URI, or unknown on a miss), plus one event when it starts blocking a 404 loop (tool name and block length). It never records your API key or any resource data, and drops tool arguments except on the guide and concept tools (list-guides, read-guide, lookup-concept, search-concepts), where it keeps the guide id, concept name or search words, plus the kind of guide read. Your identity is an irreversible salted hash. To opt out, send the header X-Runpod-Analytics: off — e.g. append --header "X-Runpod-Analytics: off" to the claude mcp add command. Running locally, nothing is ever sent.

Run locally with npx

Run the server as a local stdio process with your own API key:```bash
RUNPOD_API_KEY=YOUR_API_KEY npx -y @runpod/mcp-server@latest


### Local client setup

Local clients launch the `stdio` server and set `RUNPOD_API_KEY` in the environment.

**Claude Code:**```bash
claude mcp add runpod -s user \
  -e RUNPOD_API_KEY=YOUR_API_KEY \
  -- npx -y @runpod/mcp-server@latest

Use -s project for a project-local server. Verify with claude mcp list; in a session, /mcp reconnects.

Claude Desktop, Cursor, VS Code, Windsurf, and other clients — use the same command in the client's MCP config:```json
{
"mcpServers": {
"runpod": {
"command": "npx",
"args": ["-y", "@runpod/mcp-server@latest"],
"env": {
"RUNPOD_API_KEY": "YOUR_API_KEY"
}
}
}
}


Claude Desktop's config lives at `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) or `%APPDATA%\Claude\claude_desktop_config.json` (Windows); restart the app after saving. For a broader list of clients, see the MCP clients directory.

## Usage examples

Ask your MCP client in natural language:```text
List all my Runpod Pods.
``````text
Create a Runpod Pod named test-pod with image
runpod/pytorch:2.1.0-py3.10-cuda11.8.0-devel-ubuntu22.04,
GPU type NVIDIA GeForce RTX 4090, 1 GPU.
``````text
Create a Serverless endpoint named my-endpoint with image
runpod/test-output:0.0.1, GPU pool AMPERE_80, 0 min workers, 3 max workers.

Endpoints are image-based — pass an image and a GPU pool (a pool value from list-gpu-types), not a template.

See docs/configuration.md for host overrides, private image pull (registry credentials vs ECR delegation), and large-output handling.

Upgrading from 3.x

Eight tools follow their spec operationIds (e.g.
create-container-registry-auth → create-registry, get-billing →
list-billing) and start-pod/stop-pod/restart-pod fold into
pod-action with an action argument. The full old→new map is
specgen/old-mcp-tools.yaml. The server is
v2-only; RUNPOD_REST_VERSION and the v1 fallback are retired.

Security

This server acts with the full permissions of the supplied API key.

  • Never share your API key.
  • Be deliberate with destructive tools. Every tool carries MCP annotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) derived from the operation it wraps, so a host can auto-approve reads and gate delete-pod or purge-endpoint-queue on a human.
  • Each request authenticates with its own caller-supplied token, which is forwarded to the Runpod API and never persisted server-side. The server never holds a credential of its own and never shares one across users.

Local development```bash

git clone https://github.com/runpod/runpod-mcp.git
cd runpod-mcp
pnpm install
pnpm build


Run the local build directly:```bash
RUNPOD_API_KEY=YOUR_API_KEY node dist/stdio.mjs

After changes:bash pnpm type-check pnpm lint pnpm test # offline unit suite — no network or API key required pnpm build

Tools are generated from the vendored v2 OpenAPI spec rather than hand-written: see specgen/DESIGN.md for the walkthrough and specgen/README.md for the regeneration workflow and drift gates.

The REST client the tools call, @runpod/typescript-api-sdk, lives in packages/typescript-api-sdk/ and is published to npm separately. The vendored spec is in that package; both the SDK types and the MCP tools generate from it.

This project uses changesets for versioning and npm publishing; every PR with user-facing changes needs a changeset. See CLAUDE.md and docs/context.md for full contributor guidance, architecture, and the test suite.

License

Apache-2.0. The SDK in packages/typescript-api-sdk/ is MIT-licensed; see its LICENSE.

JavaScript API migration

This major release removes the @runpod/mcp-server/tools package export and
its registerTools API. The legacy registration API is not compatible with
the new generated surface. Applications should connect to the server through
MCP using the runpod-mcp CLI, or use handleMcpRequest from
@runpod/mcp-server/http when embedding the HTTP handler. The HTTP entry point
also no longer re-exports the legacy registerTools or ToolContext.

An HTTP host that serves the directory profile can import DIRECTORY_PATH
and profileForPath from @runpod/mcp-server/profile.

The hosted service's own surface (the MCP request handler, the ALP submit and
journal handlers and the knowledge search route) is @runpod/mcp-server/hosted.
The ALP contract the Convex sink shares (route names, the once-per-account
rule and the scrubber) is @runpod/mcp-server/alp, kept free of the HTTP
handler so a Convex function can bundle it. The hosted deployment itself (the
Vercel entry point, the OAuth routes and the Convex functions) is maintained
outside this repository.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Runpod MCP Ts 怎么安装?

在客户端按下面的安装命令接入:npx -y @smithery/cli install @runpod/runpod-mcp-ts --client claude。对应的包名是 @smithery/cli。装完在客户端配置里引用同一个包或端点。

Runpod MCP Ts 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Runpod MCP Ts 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Runpod MCP Ts 需要 API Key 吗?

资料标注为无需认证,装好就能连;如果实际调用时报鉴权错误,按官方文档补上凭据。

Runpod MCP Ts 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、Windsurf、Cline、VS Code;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Runpod MCP Ts 能提供哪些能力?

资料显示能力标签包括 基础设施管理、开发工具、TypeScript、Claude。具体工具清单以官方文档为准。

Runpod MCP Ts 需要什么运行环境?

运行时为 Node.js;属于本地进程,需要在本机装好运行环境。

Runpod MCP Ts 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。