Skip to directory

About Runpod MCP

Official Runpod infrastructure MCP for managing Pods, Serverless endpoints and jobs, templates, network volumes, container registries, and resource discovery.

What you can use it for

  • manage compute Pods
  • manage serverless endpoints
  • manage templates and network volumes
  • manage container registries
Connection and setup
Hosting
hosted
Transport
Streamable HTTP
Endpoint
https://mcp.runpod.io/
Authentication
Hosted OAuth Sign in with Runpod; API key alternative. Local npm server uses a Runpod API key.

Requirements

  • Runpod account
  • Local mode requires Node.js 20+ and API key

Setup steps

  1. Hosted: add https://mcp.getrunpod.io/ as remote Streamable HTTP and complete Runpod OAuth.
  2. Local: run `npx -y @runpod/mcp-server@latest` with RUNPOD_API_KEY supplied through client environment.
  3. Refresh tools/list after authentication.
  4. Require confirmation before creating, stopping, or deleting cloud resources.
Tools 6+

Six exact identifier examples verified in Runpod publisher materials; documentation describes roughly fifty infrastructure tools spanning Pods, endpoints/jobs, templates, volumes, registries, GPU/CPU discovery, and billing. Hosted availability may differ by session/account.

  • create-pod

    Create a Runpod Pod.

    01
  • list-endpoints

    List Serverless endpoints.

    02
  • create-endpoint

    Create a Serverless endpoint.

    03
  • list-pods

    List Pods.

    04
  • delete-pod

    Delete a Pod.

    05
  • list-templates

    List templates.

    06

This server’s available tools can vary by account, permissions, or configuration. The list shown is not its full runtime catalog.

Limitations and notes
  • MCP exposes cloud resource changes, including create, stop, and delete; use confirmation gates.
  • Hosted OAuth avoids a local runtime; local package requires Node.js 20+.
Original sources

Documentation checked 2026-10-28T19:00:00.000Z. Connection has not been runtime tested.