How to connect RunPod to Claude

Connect Claude Web, Desktop and Cowork to RunPod MCP. Launch a new gpu pod for inference, get status of all active pods, and more using natural language, with authentication handled for you.

RunPod logoRunPod
Api Key

RunPod is a GPU cloud platform designed for AI and machine learning workloads. Instantly access scalable compute power for demanding AI tasks.

13 Tools

Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.

This guide walks you through the easiest and most secure way to connect your RunPod account to Claude via Composio Connect, enabling it to launch a new GPU pod for inference, get status of all active pods, stop a running pod with ID 12345, and more such actions on your behalf without compromising your account security.

Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

Also integrate RunPod with

Connecting RunPod to Claude Web, Desktop, and Cowork

Two ways to add the Composio connector. Pick whichever you prefer.

1. Add with one click

Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.

Add to Claude

Add manually

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

2. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Web, Desktop, and Cowork

3. Connect your RunPod account

Back in Claude, ask it to connect to RunPod or give it any RunPod-related task.

For example, ask Claude to:

  • "Launch a new GPU pod for inference"
  • "Get status of all active pods"
  • "Stop a running pod with ID 12345"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Claude, and your RunPod account is ready to use.

What is the RunPod Claude Connector, and what's possible with it?

The RunPod MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your RunPod account. It provides structured and secure access so your agent can perform RunPod operations on your behalf.

Troubleshooting

1. Why does Claude not use the Composio connector for RunPod?

The connector can show as connected, but Claude must use it in each RunPod conversation.

  • Click + at the lower left of the chat, or type /.
  • Hover Connectors.
  • Turn on Composio.
  • Ask Claude to connect to RunPod again.

2. Why does Claude show an MCP server error before RunPod connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for RunPod.

  • Check that the connector URL is https://connect.composio.dev/mcp.
  • Connectors run from Anthropic's cloud, so your device network is usually not the problem.
  • Add the connector again from Customize > Connectors, then ask Claude to connect RunPod.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the RunPod authorization link not work?

The Composio connector is one server. Your RunPod account connects separately when Claude asks for it.

  • If the browser does not open, or the link expires, ask Claude to retry the RunPod connection.
  • Composio creates a fresh RunPod authorization link.
  • Open that link in your browser and finish the RunPod sign-in.

4. Why do RunPod actions fail after they worked before?

The RunPod connection can expire or lose permission.

  • Ask Claude to inspect the RunPod connection.
  • If the connection is unhealthy, disconnect it when Claude prompts you.
  • Reconnect the RunPod account and retry the action.
  • If Claude shows a permission prompt, approve it before Claude changes data in RunPod.
  • If the action still fails with a permission error, check that the connected account has that permission in RunPod itself.

5. How do I switch to a different RunPod account?

Claude can manage the RunPod connection for you.

  • Ask Claude to disconnect or delete the current RunPod account.
  • Ask Claude to connect RunPod again.
  • Open the new Composio authorization link for RunPod.
  • Sign in with the other RunPod account in the browser.
  • After the account connects, ask Claude to retry the RunPod task.

6. Why is my RunPod connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your RunPod connection works in Claude Web, Desktop, and Cowork.

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click and click Clear cache.
  • If RunPod tools still do not appear, click , disconnect, remove the connector, and add it again.
  • On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect RunPod.
TOOLS

Supported Tools

Every RunPod action and event your agent gets out of the box.

Create RunPod Cluster

Tool to create a new GPU cluster for multi-node distributed computing workloads on RunPod.

Create Secret

Tool to create a new secure secret in RunPod for credential management.

Delete Container Registry Authentication

Tool to delete container registry authentication from RunPod.

Delete Template

Tool to remove a RunPod template via GraphQL mutation.

Get GPU Types

Tool to retrieve available GPU types and their specifications, pricing, and availability from RunPod.

Get authenticated user info

Retrieve basic information about the authenticated user including ID, email, and security settings.

Get Pod Details

Retrieve details of a specific RunPod pod by its unique pod ID.

List CPU Types

Tool to retrieve available CPU types and their specifications from RunPod.

Save Serverless Endpoint

Tool to create or update a RunPod serverless endpoint with GPU configuration and scaling settings.

Save Container Registry Authentication

Tool to save container registry authentication credentials for accessing private Docker images in RunPod.

Save Template

Tool to create a new RunPod template or update an existing one with container configuration.

Update Registry Auth

Tool to update existing container registry authentication credentials in RunPod.

Update User Settings

Tool to update current user settings (e.

FAQ

Frequently asked questions

With a standalone RunPod MCP server, the agents and LLMs can only access a fixed set of RunPod tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from RunPod and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right RunPod tools.

Yes, absolutely. You can configure which RunPod scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your RunPod data and credentials are handled as safely as possible.

Start with RunPod.It takes 30 seconds.

Managed auth, hosted MCP servers, and every RunPod tool your agent needs.Free to start.

Start building