- Runpod API MCP server: Manage Pods, endpoints, templates, volumes, and registries through the Runpod REST API. Authenticate with Sign in with Runpod or a Runpod API key.
- Runpod docs MCP server: Search Runpod documentation for features, code examples, and guides. No authentication required.
Runpod API MCP server
The Runpod API MCP server gives AI tools access to the Runpod REST API, letting you create and manage Pods, Serverless endpoints, templates, network volumes, and container registries through natural language. Hosted endpoint:https://mcp.runpod.io/ (Streamable HTTP transport)
https://mcp.getrunpod.io/ is the same server under its old name, and it still works. Older versions of the installer and the Runpod plugin used that address. Use https://mcp.runpod.io/ for new connections. Register only one of them: each address has its own sign-in, so registering both gives you two separate entries.
Local package: @runpod/mcp-server (via npx)
Source code: github.com/runpod/runpod-mcp
Authentication: Sign in with Runpod (OAuth) for the hosted server, or a Runpod API key for the local server or as a hosted-server override.
You can connect in two ways: the recommended hosted server, or a local server that runs from an npm package with an API key.
Hosted server (recommended)
The hosted server runs athttps://mcp.runpod.io/ and provides the same capabilities as the local server. OAuth-capable clients run a “Sign in with Runpod” flow on first connect: a browser opens, you log in to the Runpod console and approve the request, and the server obtains a session-scoped API key. Nothing is stored on disk. Sign-in always starts from your client. Opening https://mcp.runpod.io/ directly in a browser doesn’t sign you in; it returns HTTP 405.
Sign-in works in Claude, ChatGPT, Codex, and Cursor, and in any client that receives the sign-in on a local address (http://localhost or http://127.0.0.1). Other clients may fail with a redirect_uri is not allowed error. For those clients, pass an API key as a header or use the local server.
The guided installer is the recommended path for supported clients. It detects your installed clients (Claude Code, Claude Desktop, Cursor, Windsurf, VS Code, opencode, and Pi) and configures each one, handling client-specific config-key differences automatically:
--client (separate several with commas). --list shows each client’s id and where its config file lives:
npx @runpod/mcp-server@latest remove.
Claude Code (hosted)
Cursor (hosted)
Add the following to.cursor/mcp.json (project-level) or ~/.cursor/mcp.json (global), or run npx @runpod/mcp-server@latest add --client cursor. Then restart Cursor and connect runpod under Settings > MCP:
opencode (hosted)
opencode uses themcp key, not mcpServers, and needs "type": "remote". Add this to opencode.json, or run npx @runpod/mcp-server@latest add --client opencode:
opencode mcp auth runpod to sign in, and opencode mcp list to check the connection.
Claude Desktop (hosted)
- Open Settings in Claude Desktop.
- Navigate to Connectors and select Add custom connector.
- Enter
https://mcp.runpod.io/as the URL and click Add.
VS Code with Copilot (hosted)
- Open the Command Palette (Ctrl+Shift+P on Windows/Linux or Cmd+Shift+P on macOS).
- Run MCP: Add Server and select HTTP.
- Enter
https://mcp.runpod.io/as the URL andRunpodas the name. - Select Global or Workspace and click Add.
Other clients (hosted)
For any other MCP-compatible client, use the remote URLhttps://mcp.runpod.io/:
Use an API key with the hosted server
To skip the OAuth flow, or if your client can’t complete it, pass your API key as a bearer header. For example, in Claude Code:headers block instead:
Local server (API key)
Use this method to run the server locally with an API key stored in your client config. For example, use it if your client doesn’t support the hosted server’s sign-in flow, or you prefer to manage the credential yourself.Supported clients
Claude Code
your_api_key_here with your Runpod API key. The --scope user flag makes the server available across all your projects. Run /mcp inside Claude Code to verify the connection.
Codex CLI
Codex CLI is OpenAI’s terminal-based coding agent.Cursor
Add the following to.cursor/mcp.json (project-level) or ~/.cursor/mcp.json (global). This configuration works with both the Cursor IDE and the Cursor Agent:
VS Code with Copilot
- Open the Command Palette (Ctrl+Shift+P on Windows/Linux or Cmd+Shift+P on macOS).
- Run MCP: Add Server and select stdio.
- Enter the following details:
- Name:
Runpod - Command:
npx - Arguments:
-y @runpod/mcp-server@latest
- Name:
- Add environment variable
RUNPOD_API_KEYwith your Runpod API key. - Select Global or Workspace and click Add.
Claude Desktop
Add the following to your Claude Desktop config file:- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
Windsurf
Edit~/.codeium/windsurf/mcp_config.json (or open from Settings > Cascade > MCP Servers > View raw config):
Cline
Open the Cline sidebar in VS Code, click the MCP Servers icon, then select Configure MCP Servers to editcline_mcp_settings.json:
Gemini CLI
Add to~/.gemini/settings.json (global) or .gemini/settings.json (project-level):
Other clients
For any other MCP-compatible client, use the following connection details:- Command:
npx - Args:
-y @runpod/mcp-server@latest - Environment:
RUNPOD_API_KEY=your_api_key_here
Usage examples
Once connected, you can interact with your Runpod resources using natural language:Runpod docs MCP server
The Runpod docs MCP server provides access to Runpod’s documentation knowledge base, making it easier to get answers about features and how to use them. Endpoint:https://docs.runpod.io/mcp
Authentication: None required
Claude Code
Codex CLI
Cursor
Add to your.cursor/mcp.json file:
VS Code with Copilot
- Open the Command Palette (Ctrl+Shift+P on Windows/Linux or Cmd+Shift+P on macOS).
- Run MCP: Add Server and select HTTP.
- Enter
https://docs.runpod.io/mcpas the URL andRunpod Docsas the name. - Select Global or Workspace and click Add.
Claude Desktop
- Open Settings in Claude Desktop.
- Navigate to Connectors and select Add custom connector.
- Enter
https://docs.runpod.io/mcpas the URL and click Add.
Windsurf
Add to~/.codeium/windsurf/mcp_config.json:
Cline
Add tocline_mcp_settings.json:
Gemini CLI
Add to~/.gemini/settings.json. Note that Gemini CLI uses httpUrl instead of url:
Other clients
For any other MCP-compatible client, use URLhttps://docs.runpod.io/mcp (HTTP transport).