> ## Documentation Index
> Fetch the complete documentation index at: https://runpod-b18f5ded-lg-endpointlogs-453.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Agent skills for AI coding tools

> Manage GPU workloads on Runpod with coding agents like Claude Code, Codex, and Cursor. Review setup steps and core concepts for building on Runpod.

The Runpod skills plugin teaches your coding agent how to run GPU workloads on Runpod. Once installed, you can ask your agent to create Pods, deploy Serverless endpoints, transfer files, or deploy your own code with Flash, all in natural language. A built-in router sends each request to the right skill, so you don't need to know which tool applies.

It works with [Claude Code](https://docs.anthropic.com/en/docs/claude-code), [Codex](https://github.com/openai/codex), [Cursor](https://www.cursor.com/), [GitHub Copilot](https://github.com/features/copilot), [Windsurf](https://codeium.com/windsurf), [Cline](https://github.com/cline/cline), and [many other AI agents](https://skills.sh/).

## Quick start

Install the skills with a single command that works with every agent:

```bash theme={null}
npx skills add runpod/runpod-plugins-official
```

Next, install the Runpod CLI that the skills rely on (skip this if you already have it):

```bash theme={null}
curl -sSL https://cli.runpod.net | bash
# or with Homebrew:
brew install runpod/runpodctl/runpodctl
```

Then authenticate with your [Runpod API key](/get-started/api-keys). The same key works for the CLI, Flash, and the bundled MCP server:

```bash theme={null}
# Set the key for the current shell (add to ~/.zshrc or ~/.bashrc to persist):
export RUNPOD_API_KEY=<key>

# Or save it permanently to ~/.runpod/config.toml:
runpodctl doctor
```

That's it — restart your agent and [get started](#getting-started).

## Getting started

There are no commands to memorize: describe what you want, and the router picks the right skill (prompting you if something like an API key is still missing). Confirm it's wired up by asking:

* "List my Runpod endpoints"

If your endpoints come back, you're set — see [What you can do](#what-you-can-do) for more examples.

## What's included

The plugin installs a router and a set of focused skills:

| Skill              | Description                                                                                                                               |
| ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------- |
| **runpod**         | Router and entry point. Reads your task and hands it to the right skill.                                                                  |
| **runpod-mcp**     | Manages Pods, endpoints, templates, network volumes, registries, and billing through the Runpod MCP server.                               |
| **runpodctl**      | Manages the same resources from the [Runpod CLI](/runpodctl/overview), plus Hub deployments, file transfers, SSH keys, and model caching. |
| **flash**          | Writes and deploys your own Python code to Runpod Serverless using the [runpod-flash](/flash/overview) SDK.                               |
| **companion-clis** | Uses supporting CLIs such as Hugging Face, Docker, and the AWS CLI when a task needs them.                                                |
| **runpod-usage**   | Provides conceptual knowledge about Pods, Serverless, storage, and GPU selection.                                                         |

The plugin also includes a collection of worked, end-to-end reference tasks, such as deploying a Whisper endpoint or running a model on a Pod, that guide your agent through common workflows.

## What you can do

Once installed, you can ask your agent to perform tasks like the following:

| Category          | Example prompt                                    |
| ----------------- | ------------------------------------------------- |
| Create resources  | "Create a Pod with an RTX 4090"                   |
| List resources    | "List my Pods" or "Show my Serverless endpoints"  |
| GPU availability  | "What GPUs are available?"                        |
| Account info      | "Show my account balance"                         |
| Deploy endpoints  | "Deploy a Serverless endpoint using my template"  |
| Manage Pods       | "Stop my Pod" or "SSH into my Pod"                |
| Deploy with Flash | "Deploy this function to a remote GPU with Flash" |
| Local development | "Start a local dev server with Flash"             |

## Native install options

The `npx skills add` command above works everywhere. If you'd rather install the plugin through your agent's native marketplace, use the route for your agent below. Each route installs the same router and skills.

### Claude Code

Add the marketplace, install the plugin, then reload:

```bash theme={null}
/plugin marketplace add runpod/runpod-plugins-official
/plugin install runpod@runpod
/reload-plugins
```

Installing the plugin also wires up the hosted Runpod MCP server. To authenticate it, run `/mcp`, select **runpod**, and choose **Sign in with Runpod**.

### Codex

```bash theme={null}
codex plugin marketplace add https://github.com/runpod/runpod-plugins-official.git
```

Run `codex /plugins`, open the **Runpod** tab, and install (reload if prompted). If the Runpod MCP tools don't appear, add the hosted server manually:

```bash theme={null}
codex mcp add runpod --transport http https://mcp.getrunpod.io/
```

### Gemini

Gemini can install the plugin natively through the bundled `gemini-extension.json`. Follow your client's extension documentation to add it.

## Connecting the MCP server on other agents

The hosted Runpod MCP server gives your agent structured control-plane tools for managing Pods, endpoints, and other resources. Claude Code sets it up automatically during a native install. On other agents, run the guided installer, which detects your agent and configures the connection:

```bash theme={null}
npx @runpod/mcp-server@latest add
```

The installer authenticates the MCP server for you. To reuse the API key you already set instead, pass it as a bearer header when you add the server. For example, in Claude Code:

```bash theme={null}
claude mcp add --transport http runpod -s user https://mcp.getrunpod.io/ \
  --header "Authorization: Bearer $RUNPOD_API_KEY"
```

## Update and uninstall

To update the plugin to the latest version:

```bash theme={null}
# Claude Code:
/plugin marketplace update runpod

# Codex:
codex plugin marketplace upgrade runpod

# skills.sh:
npx skills add runpod/runpod-plugins-official
```

In Claude Code, run `/reload-plugins` after updating.

To uninstall:

```bash theme={null}
# Claude Code:
/plugin uninstall runpod@runpod

# Codex:
codex plugin marketplace remove runpod

# skills.sh:
npx skills remove runpod
```

If a command reports a name mismatch, list what's installed first with `/plugin marketplace list` (Claude Code), `codex plugin marketplace list` (Codex), or `npx skills list` (skills.sh), then use the name shown.

## Learn more

<CardGroup cols={2}>
  <Card title="Runpod skills repository" href="https://github.com/runpod/runpod-plugins-official" icon="github" horizontal>
    Source code and full skill definitions.
  </Card>

  <Card title="skills.sh" href="https://skills.sh/" icon="wand-magic-sparkles" horizontal>
    The skills platform with the full list of compatible AI agents.
  </Card>

  <Card title="Runpod CLI reference" href="/runpodctl/overview" icon="terminal" horizontal>
    Full runpodctl documentation.
  </Card>

  <Card title="MCP servers" href="/get-started/mcp-servers" icon="plug" horizontal>
    Another way to integrate AI tools with Runpod.
  </Card>
</CardGroup>