runpod

Runpod Official Plugins

The official plugin marketplace of skills for AI agents to manage GPU workloads on Runpod — pods, serverless endpoints, jobs, templates, and volumes — via the Runpod MCP server, runpodctl, and flash.

This repo ships one plugin, runpod, that bundles a router plus six skills, the hosted Runpod MCP server config, and worked golden paths.

Compatibility: installs as a native plugin in Claude Code, Codex, Gemini, and opencode (with auto-update), and as skills via skills.sh for Cursor, Copilot, Windsurf, Cline, and 17+ other agents — all from the same manifest.

Quick start

Install — works with every agent (Claude Code, Codex, Cursor, Copilot, Windsurf, Cline, Gemini, opencode, +more). The first line is all you need; drop any others you won't use:

npx skills add runpod/runpod-plugins-official # the skills — any agent (essential)
curl -sSL https://cli.runpod.net | bash       # runpodctl — infra CLI (or: brew install runpod/runpodctl/runpodctl)
uv tool install runpod-flash                  # flash — deploy your own code (optional; or: pip install runpod-flash)
npx @runpod/mcp-server@latest add            # hosted MCP server — guided setup, OAuth (optional)

Then authenticate — one API key covers everything (from the console):

export RUNPOD_API_KEY=<key>      # current shell only — add to ~/.zshrc (or ~/.bashrc) to persist
# or, to save it permanently:
runpodctl doctor                 # prompts for the key and writes ~/.runpod/config.toml

Now just ask in plain English — the skill drives the tools for you:

"list my Runpod endpoints" · "spin up an A100 pod" · "deploy this handler to serverless"

That's it. Notes:

• Claude Code can install natively instead (auto-wires the hosted MCP server + OAuth) — see Install → Claude Code. MCP auth details: Authentication.
• Companion CLIs (docker/gh/hf/aws) install separately, per task — see companion-clis.

Install

Same repo, one manifest — pick your agent below. Every route installs the same router + six skills, plus a hosted Runpod MCP server for control-plane tools. Then authenticate.

Claude Code

/plugin marketplace add runpod/runpod-plugins-official
/plugin install runpod@runpod
/reload-plugins

Installing also wires up the hosted Runpod MCP server (via the bundled .mcp.json) — no separate MCP setup. Authenticate it: /mcp → runpod → Sign in with Runpod (OAuth; no key on disk).

Verify: /plugin shows Runpod under Installed; then ask "list my Runpod endpoints" — it should call the MCP list-endpoints tool.

Codex

codex plugin marketplace add https://github.com/runpod/runpod-plugins-official.git
codex /plugins        # → open the "Runpod" marketplace tab → Runpod → Install (reload if prompted)

Manage the source: codex plugin marketplace list · … upgrade runpod · … remove runpod.

Codex may not auto-wire the bundled MCP — if the runpod MCP tools don't appear after install, add the hosted server manually:

codex mcp add runpod --transport http https://mcp.getrunpod.io/

Verify: ask a Runpod task (the skill/router should answer); once the MCP is added, "list my Runpod endpoints" should call a tool.

Everything else — Cursor, Copilot, Windsurf, Cline, opencode, Gemini (+17)

Install the skills via skills.sh (reads the same .claude-plugin/marketplace.json):

npx skills add runpod/runpod-plugins-official
# just one skill:
npx skills add https://github.com/runpod/runpod-plugins-official/tree/main/plugins/runpod/skills/runpodctl

Gemini can also install natively via the bundled gemini-extension.json (see your client's extension docs). For these clients, add the MCP server yourself — the guided installer configures most agents:

npx @runpod/mcp-server@latest add     # detects your agent + sets up the hosted MCP (OAuth)

See runpod-mcp/SKILL.md for hosted vs local (stdio) MCP setup and all client options.

Authentication

Auth is needed in two places, and one Runpod API key covers both:

What	What it needs	How
runpodctl + flash (the CLIs)	RUNPOD_API_KEY (env or saved)	export RUNPOD_API_KEY=<key>, or runpodctl doctor to save it
Hosted Runpod MCP server (infra tools)	OAuth or the same key	/mcp sign-in, or pass the key as a Bearer header

Fastest path — one key, everything: