vastai-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VAST_API_KEY | Yes | Your Vast.ai API key. Get one at https://cloud.vast.ai (Settings -> API Keys). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_gpusA | Show the current snapshot of all available GPUs on Vast.ai: total supply, available count, and 10th/median/90th percentile pricing per GPU model. |
| search_offersA | Search rentable GPU machine offers on Vast.ai. Returns offers with id (ask_id), gpu_name, num_gpus, price per hour (dph_total), disk, region, bandwidth, verification and reliability. Use the returned offer id with create_instance. |
| create_volumeA | Rent a new persistent volume on Vast.ai. The volume is billed separately from instances. Returns the new volume name/id. |
| list_volumesA | List all volumes currently rented by you. |
| create_instanceA | Create (rent) a new instance on a specific machine offer (ask id from search_offers), optionally creating and attaching a new volume. Returns the new contract/instance id. Requires max_hourly_price as a spend guardrail: the offer's live price is checked against it and the rental is refused if the price exceeds the cap or can't be verified. |
| billing_summaryA | Overall billing: per-instance hourly cost breakdown (GPU, disk, storage, total $/hr) plus the most recent charges. days limits the charge lookback window. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct resource or action: GPU pricing snapshots, rentable offers, volume creation, volume listing, instance creation, and billing. list_gpus and search_offers are related but clearly differ in granularity, and the descriptions prevent confusion.
Most tool names follow a clear verb_noun pattern such as list_gpus, create_volume, and create_instance. billing_summary is the only real outlier, being a noun phrase rather than a verb-led action, but the overall convention remains predictable.
Six tools is well within the ideal scope for a focused rental-management server. Each tool serves a necessary step in the core workflow, and there is no obvious bloat or redundancy.
The tool set covers discovery, creation, volume listing, and billing, but it lacks essential lifecycle operations such as listing instances, terminating instances, and deleting volumes. This creates significant dead ends: resources can be created but not managed or cleaned up.