LabscoMCP early access ↗
CryDevOkMCP SERVER

Vast.ai

Rent, run and tear down Vast.ai GPU instances from the conversation — and check the balance and what is still running without opening the console.

by CryDevOk ↗Cloud Resources & Infrastructure as CodeCommunity

LABSCO SUMMARY

The rented GPU box, answerable from the window where the code is.

Vast.ai's whole failure mode is the instance you forgot was running. What it costs you and what is still up become questions you ask, rather than a browser tab you remember to open.

What it is

An MCP server for the Vast.ai GPU cloud. It authenticates with your Vast.ai API key and, for anything that needs a shell on the box, your SSH key pair. Its tools cover the account, a search of GPU offers, the instance lifecycle — create, start, stop, reboot and destroy — and shell commands on a running box over SSH.

What you get

  • Your account as the API sees it — username, email, user ID, current balance and total spent
  • The SSH key information Vast.ai holds for you
  • Your instances listed by state, so you can see what is still burning credit
  • Instances rented and run from the conversation — offers searched, instances created, started, stopped, rebooted and destroyed, and commands run on them over SSH

Requirements

A Vast.ai API key from Account → API Keys at console.vast.ai, set as VAST_API_KEY. Install with uv: uv sync, then uv tool install -e .. For anything that needs a shell on the instance, point SSH_KEY_FILE and SSH_KEY_PUBLIC_FILE at your key pair and tighten the private key's file permissions — the README describes SSH keys as needed for full functionality.

Setup effort

Build from source — git clone https://github.com/CryDevOk/vastai-mcp.git