Vast.ai MCP connector
The Vast.ai connector lets Claude, ChatGPT, Cursor, Microsoft Copilot and any MCP client rent and manage GPU instances, network disks, SSH keys, worker groups, endpoint jobs and secrets in Vast.ai, with every action running under the person who signed in.
- Connects with an API key
- Free 14-day trial
- No credit card
List every running Vast.ai instance and its bid price
Working in Vast.ai with Elaichi
-
List all Vast.ai instance sshes
-
List all Vast.ai auth apikeys
-
List all Vast.ai workergroups
How to connect Vast.ai to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Vast.ai 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.
Vast.ai 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.
Vast.ai 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.
Vast.ai 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.
Vast.ai 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 Vast.ai 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 Vast.ai through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Vast.ai is logged.
-
Machine learning
Spin up a GPU box for training
Ask for a new instance with the right disk and SSH access, then adjust the bid price if the job needs to keep running through a busy hour.
-
Data engineering
Move datasets onto a network disk
Create a network disk for a project and queue a copy of training data onto it with an rclone command, then clear the command when the transfer is done.
-
Platform
Keep worker groups and endpoint jobs in shape
List the worker groups serving a model, change the settings on one, and add or retire endpoint jobs as traffic changes.
-
Security
Rotate API keys and secrets without a console
See which Vast.ai API keys exist, create a fresh one for a new pipeline, and delete keys and secrets that are no longer needed.
-
Finance
Trim spend on running instances
Review what is running, lower the bid price on instances that can wait, and remove SSH access from boxes that are being wound down.
-
Hosting
Take a machine in and out of maintenance
Cancel scheduled maintenance on a host machine when the fix lands early, or run a cleanup on a machine before it goes back into the market.
Try asking
- “List every running Vast.ai instance and its bid price”
- “Which Vast.ai machines are in maintenance right now”
- “Show network disks attached to instances in Research”
What connecting Vast.ai gets you
6 screens from Elaichi, each doing one job for your Vast.ai account.
Ask Elaichi to work across your apps.
List every running Vast.ai instance and its bid price
Which Vast.ai machines are in maintenance right now
Show network disks attached to instances in Research
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Vast.ai instances in plain language.
Answers come from live Vast.ai instances, machines and network disks, not stale exports.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Vast.ai here.
One org MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
89 Vast.ai tools ready with no custom code.
Instances, SSH keys, machines, network disks, bid prices and rclone commands, all callable.
Toolboxes
Each team gets its own Vast.ai toolbox.
Curate one toolbox of Vast.ai tools per team and expose only that.
Shared connections
Teammates use Vast.ai accounts without seeing keys.
Every connection shows who connected it and which teams and members share it.
Audit log
Every Vast.ai call is written down.
When, who, what happened, type and resource, appended for each instance and disk.
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.
Vast.ai digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch instances
Vast.ai
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
Vast.ai
Queued
Automations
A schedule starts real Vast.ai work.
Fetch instances, group them, draft a digest, get approval, post back to Vast.ai.
Vast.ai health
Refreshed 4 minutes ago · every 15 minutes · from the instances collection
Instances
1,284 ↓ 12%
Machines
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Instances created
Last 14 days
By team
Share of activity
ML Research 34%
Platform Engineering 27%
MLOps 21%
Data Engineering 18%
Collections and dashboards
Vast.ai numbers land before anyone asks.
Four metrics, 14 days of instances created and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Vast.ai
All three can connect Vast.ai 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 Vast.ai tools | Allow or restrict single Vast.ai 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 Vast.ai 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.
Vast.ai tools for your AI agents
89 tools are ready to call through Elaichi's MCP endpoint the moment you connect Vast.ai, 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 Vast.ai to Claude?
First connect Vast.ai in Elaichi by pasting an API key from your Vast.ai account, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Vast.ai signs in with an API key, so there is no OAuth application to register and no client ID or secret to generate. Once both steps are done, Claude can work with your Vast.ai instances, disks and keys as you.
Does Vast.ai work with ChatGPT and Cursor as well as Claude?
Yes. Vast.ai is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, is pasted into Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. There is nothing extra to set up for each client.
What can an AI agent actually do with my Vast.ai account?
An agent can create Vast.ai instances and network disks, add or remove SSH access, change the bid price on a running instance, and queue copy or rclone commands to move data. It can also list, create, update and delete worker groups, endpoint jobs, API keys and secrets, and take a host machine out of maintenance or run a cleanup on it. Short, concrete asks such as "lower the bid on instance 4821" work better than long paragraphs.
Does connecting Vast.ai give the AI access to everything in my account?
No. Every call to Vast.ai runs under the API key the signed-in person provided, so the agent can only reach the instances, disks, worker groups and secrets that key can already reach. Elaichi can narrow that further by restricting specific actions, and it never widens what the key allows.
Can I stop an agent from deleting or changing things in Vast.ai?
Yes. Restrictions in Elaichi work per action, so you can allow listing Vast.ai instances and worker groups while restricting deletion of instances, API keys or secrets. 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 Vast.ai connection when someone leaves?
Offboarding that person in Elaichi ends their access to Vast.ai through every client at once. If they had shared a Vast.ai connection, it keeps working for everyone else on the team. Disconnecting Vast.ai once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client together.
Does the Vast.ai MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Vast.ai 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 Vast.ai?
Yes. Both let Claude, ChatGPT or Cursor use Vast.ai. 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 Vast.ai call.
How is Elaichi different from Composio for Vast.ai?
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 Vast.ai: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Vast.ai 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