runpod-mcp SKILL.md skillA

runpod-mcp from runpod/runpod-plugins-official is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add runpod/runpod-plugins-official/runpod-mcp@"1.8.0" # x-release-please-version

Pins "1.8.0" # x-release-please-version in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

runpod/runpod-plugins-official

Path

plugins/runpod/skills/runpod-mcp/SKILL.md

Versions recorded

11

Latest version

"1.8.0" # x-release-please-version, committed Oct 19, 2026

First version recorded

Oct 9, 2026

Size

15,446 bytes

Repository stars

46

License

Apache-2.0

Manage Runpod infrastructure through the connected Runpod MCP server's tool calls (pods, serverless endpoints and jobs, templates, network volumes, registry credentials, secrets, clusters, the GPU/CPU catalog, and billing), and connect the server when it is missing (hosted or local npx). Load it before the first Runpod MCP tool call of a request: it routes the task to the journey skill that carries the procedure, owns the answer contract and the rules on which resources you may change, and…

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Runpod MCP

The Runpod MCP server exposes Runpod's control plane as structured tool calls, so an
MCP-capable agent can manage infrastructure without shelling out. It is the same Runpod
REST API that `runpodctl` uses. Pick MCP when its tools are connected (typed params,
structured errors, no shell quoting).

This skill does three things: it connects the server, routes each request to the
journey skill that carries its procedure ([Route by intent](#route-by-intent)), and owns
the **answer contract** below, which every reply follows.

**For a multi-step job, read the worked example before calling tools.** Tool calls are
easy to issue and easy to issue in the wrong order. The verified end-to-end sequences
live in [runpod/golden-paths/README.md](../runpod/golden-paths/README.md) (image →
template → endpoint, pod → volume → serverless, multi-region, autoscaling, monitoring).
The journey skills cover procedure within one journey; the paths cover what order to do
a whole job in.

## Connect

Connect the hosted server with **your API key as a Bearer header** if you also use runpodctl/flash. That one key auths the MCP *and* the CLIs (the 80% path):

```bash
…

Read the whole file at its exact version.

How to install

mdr add runpod/runpod-plugins-official/runpod-mcp@sha256:cb909a7861077f20

[![mdr](https://markdownregistry.com/badge/art_pxwc5uipkd2a5yls.svg)](https://markdownregistry.com/a/art_pxwc5uipkd2a5yls)

Versions

The registry has recorded 11 versions of this file, between Oct 9, 2026 and Oct 19, 2026, about one every day.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_pxwc5uipkd2a5yls
GET https://markdownregistry.com/api/v1/resolve?ref=runpod/runpod-plugins-official/runpod-mcp
GET https://markdownregistry.com/api/v1/blob/cb909a7861077f200c5078eecc9d4084c2aab7b535beffc06984d848faa6d9c1

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from runpod/runpod-plugins-official

Every file in runpod/runpod-plugins-official

Browse by kind, by grade A, or by owner.