Runpod MCP connector
Connect Runpod to Claude, ChatGPT, Cursor, Microsoft Copilot, or any MCP client through Elaichi and start, stop, create, and delete Runpod pods, serverless endpoints, and templates from a chat, with each action running as the person who signed in.
- Connects with an API key
- Free 14-day trial
- No credit card
List running Runpod pods and their GPU types.
Working in Runpod with Elaichi
-
List all Runpod openapi jsons
-
List all Runpod docs
-
List all Runpod pods
How to connect Runpod to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Runpod MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Runpod MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Runpod MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Runpod MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Runpod MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Runpod to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Runpod through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Runpod is logged.
-
Machine learning
Stop idle pods before they run up the bill
Ask which Runpod pods are running right now, see who left them on, and stop the ones nobody is using without opening the Runpod console.
-
Engineering
Spin up a pod from an approved template
Create a new Runpod pod from a saved template so the GPU type, container image, and settings match what the team already agreed on.
-
Platform
Roll out a new endpoint version
Update a Runpod serverless endpoint to a new template or worker configuration, then confirm it picked up the change.
-
Finance
Reconcile what is running against the invoice
List every Runpod pod and endpoint in the account at month end and check the running ones against the charges before approving the bill.
-
Research
Restart a stuck training pod
When an experiment hangs, ask for the pod by name, reset or restart it, and get back to the run in a minute.
-
Support
Look up how Runpod handles something
Ask a question about Runpod pods, endpoints, or templates and get an answer drawn from Runpod's own docs and API reference instead of searching for it.
Try asking
- “List running Runpod pods and their GPU types.”
- “Stop idle pods in the ML research workspace.”
- “Which Runpod endpoints were created this week?”
What connecting Runpod gets you
6 screens from Elaichi, each doing one job for your Runpod account.
Ask Elaichi to work across your apps.
List running Runpod pods and their GPU types.
Stop idle pods in the ML research workspace.
Which Runpod endpoints were created this week?
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about pods, read the answer.
Plain language questions return live Runpod pods, endpoints and docs.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Runpod.
One org MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
58 Runpod tools arrive ready to call.
Pods, endpoints, docs and OpenAPI methods listed, with no custom code written.
Toolboxes
Every team gets its own Runpod toolbox.
Toolboxes are scoped per team, so ML research and platform see different tools.
Shared connections
Teammates run pods without seeing keys.
The connections table shows who connected each Runpod account and its sharing.
Audit log
Every pod start has a name on it.
When, who, what happened, type and resource for each Runpod call.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Runpod digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch pods
Runpod
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Runpod
Queued
Automations
A schedule fires, a digest posts back.
Six steps fetch Runpod pods, group them, draft, wait for approval, post.
Runpod health
Refreshed 4 minutes ago · every 15 minutes · from the pods collection
Pods
1,284 ↓ 12%
Endpoints
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Pods created
Last 14 days
By team
Share of activity
ML research 34%
Platform EU 27%
Inference prod 21%
Data engineering 18%
Collections and dashboards
Runpod health counted, not asked for.
Four metrics, 14 days of pods created, split by team, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Runpod
All three can connect Runpod to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Runpod tools | Allow or restrict single Runpod tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Runpod call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Runpod tools for your AI agents
58 tools are ready to call through Elaichi's MCP endpoint the moment you connect Runpod, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Runpod to Claude?
In Elaichi, choose Runpod from the connector list and paste in a Runpod API key, which you copy from your Runpod account settings. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in as yourself and Runpod is available in the chat.
Does Runpod work with ChatGPT and Cursor as well as Claude?
Yes. Once Runpod is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client, and the Elaichi Agent. You connect Runpod once and every client picks it up.
What can an AI agent actually do with my Runpod account?
With Runpod connected, an agent can list your pods, endpoints, and templates, create new ones, start, stop, reset, or restart a pod, update an endpoint or template, and delete what is no longer needed. It can also answer questions from Runpod's docs and API reference. Because Runpod exposes a lot of actions, short concrete asks like "stop the pod called training-3" work better than long paragraphs.
Does connecting Runpod give the AI access to my whole Runpod account?
The agent can only do what the Runpod API key it was given can do, and every call runs as the person who signed in to Elaichi. Elaichi can narrow that further, for example to viewing and stopping pods but never creating or deleting them. Elaichi never widens access beyond what the Runpod key already allows.
Can I stop an agent from deleting or changing things in Runpod?
Yes. Restrictions in Elaichi apply per action, so you can allow listing and starting Runpod pods while restricting deleting pods, endpoints, or templates. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
What happens to a Runpod connection when someone leaves?
Offboarding a person in Elaichi ends their access to Runpod immediately across every client they used. A Runpod connection shared with the team keeps working for everyone else. If you want it gone entirely, disconnecting Runpod once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client at the same time.
Does the Runpod MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Runpod is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Runpod?
Yes. Both let Claude, ChatGPT or Cursor use Runpod. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Runpod call.
How is Elaichi different from Composio for Runpod?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Runpod: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Runpod in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot