How to connect RunPod to Claude Cowork

RunPod logo
Claude Cowork logo
divider

Introduction

Cowork is Anthropic's AI agent for knowledge work. Think of it as Claude Code for everything else. It works autonomously with your computer, local files, and applications to accomplish complex tasks.

This guide walks you through the easiest and most secure way to connect your RunPod account to Cowork 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.

Also integrate RunPod with

Connecting RunPod to Claude Cowork

1. Open Customize

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

2. Add the Composio MCP server

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

3. 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 Cowork

4. Connect your RunPod account

Back in Cowork, ask the agent to connect to RunPod or give it any RunPod-related task.

For example, ask Cowork 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 Cowork, and your RunPod account is ready to use.

What is Claude Cowork?

Claude Cowork is Anthropic's agent for general knowledge work. It can use your computer, files, and connected applications to complete longer-running tasks across your work tools.

With Composio Connect, Cowork can securely access apps like RunPod through MCP without you sharing account credentials directly with the agent.

What is the RunPod MCP server, 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.

Supported Tools & Triggers

Tools
Create RunPod ClusterTool to create a new GPU cluster for multi-node distributed computing workloads on RunPod.
Create SecretTool to create a new secure secret in RunPod for credential management.
Delete Container Registry AuthenticationTool to delete container registry authentication from RunPod.
Delete TemplateTool to remove a RunPod template via GraphQL mutation.
Get GPU TypesTool to retrieve available GPU types and their specifications, pricing, and availability from RunPod.
Get authenticated user infoRetrieve basic information about the authenticated user including ID, email, and security settings.
Get Pod DetailsRetrieve details of a specific RunPod pod by its unique pod ID.
List CPU TypesTool to retrieve available CPU types and their specifications from RunPod.
Save Serverless EndpointTool to create or update a RunPod serverless endpoint with GPU configuration and scaling settings.
Save Container Registry AuthenticationTool to save container registry authentication credentials for accessing private Docker images in RunPod.
Save TemplateTool to create a new RunPod template or update an existing one with container configuration.
Update Registry AuthTool to update existing container registry authentication credentials in RunPod.
Update User SettingsTool to update current user settings (e.

Available tools and triggers

After setup, the supported RunPod tools and triggers listed on this page are available to Cowork through Composio Connect.

You can now ask Cowork to handle RunPod workflows in natural language, from quick summaries and drafting tasks to more complex multi-step work across connected apps.

How to build RunPod MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and RunPod MCP?

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.

Can I use Tool Router MCP with Claude Cowork?

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.

Can I manage the permissions and scopes for RunPod while using Tool Router?

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.

How safe is my data with Composio Tool Router?

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.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.