Runpod MCP server

Read from the package source without running it. The installed server may list more.

• create_container_registry_authwrite action

  Create a new container registry authentication credential with a unique name. This stores the username and password needed to authenticate with a container registry.

• create_network_volumewrite action

  Create a new network volume in a specified Runpod data center. The volume will be allocated with the specified storage capacity and can be referenced by its user-defined name.

• create_podwrite action
• create_serverless_endpointwrite action
• create_templatewrite action

  Create a new Docker-based template for RunPod Pods or Serverless workers. Templates define the compute environment, Docker image, runtime configuration, and exposed ports for containerized workloads.

• delete_container_registry_authwrite action

  Permanently delete a container registry authentication configuration. This removes the stored credentials and access settings for the specified registry.

• delete_endpointwrite action

  Permanently delete an endpoint by its ID. This action cannot be undone and will remove the endpoint from the system.

• delete_network_volumewrite action

  Permanently delete a network volume by its ID. This operation removes the network volume and its associated resources from the system.

• delete_podwrite action

  Permanently delete a Pod by its ID. This operation removes the Pod and cannot be undone.

• delete_templatewrite action

  Permanently delete a template by its ID. This action cannot be undone.

• get_container_registry_auth

  Retrieve a specific container registry authentication configuration by its unique identifier. Returns the complete details of the requested registry auth.

• get_endpoint

  Retrieve a single endpoint by its ID. Optionally include details about the template used to create it and the workers currently running on it.

• get_network_volume

  Retrieve a specific network volume by its unique identifier. Returns detailed information about the requested network volume.

• get_pod

  Retrieve a single Pod by its ID with optional related resource information. Use include parameters to expand the response with machine, network volume, savings plans, template, or worker details.

• get_template

  Retrieve a single template by its ID. Optionally include templates from Serverless endpoints, community-made public templates, or official Runpod templates in the response.

• list_container_registry_auths

  Retrieves a list of all container registry authentication configurations. Use this to view available registry credentials and their settings.

• list_endpoint_billing_history
• list_endpoints

  Retrieves a list of all available endpoints. Optionally include details about the templates used to create endpoints and the workers currently running on them.

• list_network_volume_billing

  Retrieve aggregated billing records for your network volumes over a specified time period. Results can be grouped by hour, day, week, month, or year.

• list_network_volumes

  Retrieves a list of all network volumes available in the system. Use this operation to discover and enumerate network storage resources.

• list_pod_billing_history

  Retrieve aggregated billing records for your Pods over a specified time period. Results can be grouped by individual Pod or GPU type, with flexible time bucket granularity.

• list_pods

  Retrieve a list of Pods with optional filtering by compute type, hardware specifications, location, status, and other attributes. Supports inclusion of related metadata such as machine details, network volumes, savings plans, and templates.

• list_templates

  Retrieve available templates with optional filtering to include endpoint-bound, community, and official Runpod templates. By default, returns only your personal templates.

• reset_pod

  Reset a Pod to its initial state, clearing any runtime state or configuration changes. This operation restarts the Pod and restores it to a clean state.

• restart_pod

  Restart a running Pod, causing it to stop and start again. This operation is useful for refreshing a Pod's state or recovering from transient issues.

• start_pod

  Start or resume a Pod that is currently stopped or paused. This operation transitions the Pod to a running state.

• stop_pod

  Stop a running Pod, halting its execution and resources. This operation gracefully terminates the Pod identified by the provided ID.

• update_endpointwrite action
• update_endpoint_asyncwrite action
• update_network_volumewrite action

  Update the name and/or storage capacity of an existing network volume. Changes take effect immediately after the update is processed.

• update_network_volume_actionwrite action

  Update the name and/or storage capacity of an existing network volume. The new size must be larger than the current allocated size.

• update_podwrite action

  Update Pod configuration settings such as Docker image, environment variables, networking, and port mappings. Changes may trigger a Pod reset depending on the parameters modified.

• update_pod_requestwrite action

  Update configuration settings for an existing Pod, including container image, environment variables, networking, and exposed ports.

• update_templatewrite action

  Update an existing template's configuration, including Docker image settings, environment variables, exposed ports, and metadata. Changes apply to all Pods created from this template going forward.

• update_template_alternatewrite action

  Update an existing Pod template's configuration, including Docker image settings, environment variables, exposed ports, and metadata. Changes apply to all Pods created from this template going forward.

• Code scan5 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 138 days ago8/15
• Maintainer identityregistry namespace matches repository owner7/10

Safety score

80/100

higher than 60% of 48,255 servers

Tools

35

the typical server has 7

Tools that change things

51%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

31

more than 92% of 28,688 servers

Downloads a week

150

more than 71% of 12,191 servers with a package

Runpod: common questions

Is Runpod MCP server safe?

Mostly: it is graded B (80/100). Read the Runpod safety report

How do I install Runpod?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Runpod need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Runpod maintained?

The last commit was 176 days ago (2026-05-12). The latest release is v1.0.1.

How does Runpod compare with other MCP servers?

safety score 80/100 (higher than 60% of 48,255 servers); tools 35 (the typical server has 7); tools that change things 51% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.