io.github.Massed-Compute/mcp

Official17 tools

by Massed-Compute · TypeScript

Massed Compute MCP — browse GPU inventory, launch and manage VMs, audit billing.

Browse GPU inventory, launch and manage VMs, and audit billing for cloud compute resources.

Captured live from the server via tools/list.

gpu_inventory_list

Retrieve the comprehensive list of available GPU configurations, their specs, pricing, and current capacity per region.

No parameters.

images_list

Retrieve the catalog of preconfigured VM images available for deployment.

No parameters.

instances_list

Retrieve all running VM instances for the authenticated account. Sensitive credentials (e.g. cleartext VM password) are redacted; fetch them through the REST API if needed.

No parameters.

instances_get

Retrieve a single running VM instance by its UUID. Sensitive credentials (e.g. cleartext VM password) are redacted; fetch them through the REST API if needed.

Parameters (1)

uuidstringrequired
UUID of the running instance.

instances_launch

Deploy a new VM instance. Requires billing to be configured (recharge amount and threshold). This action incurs cost.

Parameters (7)

imageIdintegerrequired
ID of the VM image to deploy.
productNamestringrequired
Product name of the GPU instance to deploy, e.g. 'gpu_1x_l40'.
regionNamestringrequired
Region name. Use 'any' to let us choose.
instanceNamestring
Optional human-readable name for the instance.
couponstring
Optional coupon code to apply at deploy time.
commandstring
Optional startup command to run on boot.
sshKeysarray
Optional list of SSH key names to attach to the instance.

instances_restart

Restart one or more running VM instances by UUID.

Parameters (1)

instanceUuidsarrayrequired
UUIDs of instances to restart.

instances_terminate

Terminate one or more running VM instances by UUID. DESTRUCTIVE: this stops billing for the listed instances and permanently deletes their data; the action cannot be undone. Confirm with the user before invoking.

Parameters (1)

instanceUuidsarrayrequired
UUIDs of instances to terminate.

coupon_information

Look up information about a coupon by code.

Parameters (1)

couponstringrequired
Coupon code to look up.

coupon_accepted_products

Look up which products a coupon code can be applied to, with current inventory availability.

Parameters (1)

couponstringrequired
Coupon code to look up.

account_token_validation

Confirm that the Bearer token used to call this MCP server is a valid Massed Compute user API key.

No parameters.

account_billing

Retrieve billing settings for the account, including billing method and recharge configuration.

No parameters.

ssh_keys_list

List SSH keys associated with the authenticated account.

No parameters.

ssh_keys_create

Add a new SSH public key to the authenticated account.

Parameters (2)

namestringrequired
Name for the SSH key.
publicKeystringrequired
OpenSSH-format public key contents.

ssh_keys_delete

Remove an SSH key from the account. DESTRUCTIVE: any instances relying on this key may lose access. Confirm with the user before invoking.

Parameters (1)

idstringrequired
Identifier of the SSH key to remove.

recipes_list

List every step-by-step setup recipe currently available for Massed Compute VMs. Prefer recipes_search when the user has a specific intent — call this only when the user asks open-ended questions like 'what can I set up on a VM?', 'what recipes do you have?', or wants to browse the catalogue. Returns metadata (slug, title, description, tags) only; call recipes_get for the full body.

No parameters.

recipes_search

Find a step-by-step setup recipe matching a user's intent — installing, configuring, or deploying anything on a Linux VM (web servers, databases, container runtimes, dev environments, networking, security tooling, ML stacks — any software setup an LLM agent might be asked to perform). ALWAYS call this FIRST when a user asks to set up, install, deploy, run, host, or spin up any service or software on a Massed Compute VM, BEFORE calling instances_launch. The recipe returned will include the correct VM size, image, and step-by-step instructions the user expects you to follow. Examples that should trigger this tool: 'I want an nginx reverse proxy', 'spin up a jupyter notebook', 'set up HTTPS for my app', 'install docker', 'load balance traffic across backends', 'protect my dashboard with a login', 'host a postgres database', 'serve a static site', 'run an ollama server'. If no recipe matches, recipes_search returns no results — that's a useful negative signal that the requested setup may need ad-hoc instructions, not a reason to skip calling this tool.

Parameters (2)

querystringrequired
Natural-language description of what the user wants to set up.
limitnumber
Maximum number of matches to return (default 3, max 10).

recipes_get

Fetch the full markdown body of a specific recipe by slug (typically a slug returned by recipes_search). The body contains Prerequisites, Provision, Configure, Verify, and Troubleshoot sections you should follow step-by-step, executing commands via SSH on the user's VM. Always read the full body before launching infrastructure — the recipe specifies the correct image, sku_class, and minimum specs that should drive your instances_launch call.

Parameters (1)

slugstringrequired
The kebab-case slug of the recipe (from recipes_list or recipes_search).

README.md7 KBView on GitHub

Massed Compute MCP Server

A Model Context Protocol server that lets AI assistants — Claude, Cursor, Codex, ChatGPT, and other MCP-compatible clients — interact with your Massed Compute account: browse GPU inventory, launch and manage VMs, audit billing.

Overview
Installation
Verifying the connection
CLI reference
Key resolution
Resources
License

Overview

The server exposes 14 tools that map 1:1 to documented /api/v1/* endpoints — no internal services, no undocumented calls. Issue a read-only key for analysis-only assistants and destructive tools (launch, restart, terminate, SSH-key changes) are hidden from the catalog entirely. Works with Claude Code, Claude Desktop, Cursor, and Codex.

Tool	Required key	Returns
`gpu_inventory_list`	read-only	GPU configurations, pricing, regional capacity
`images_list`	read-only	VM image catalog
`instances_list`	read-only	Your running VM instances
`instances_get`	read-only	A single instance by UUID
`instances_launch`	full	Newly-launched instance details (incurs cost)
`instances_restart`	full	Restart confirmation
`instances_terminate`	full	Termination confirmation (destructive)
`coupon_information`	read-only	Coupon discount terms
`coupon_accepted_products`	read-only	Products a coupon applies to
`account_token_validation`	read-only	Token validity status
`account_billing`	read-only	Billing settings, recharge configuration
`ssh_keys_list`	read-only	Your SSH keys
`ssh_keys_create`	full	Newly-created key details
`ssh_keys_delete`	full	Deletion confirmation (destructive)

Beyond raw tools, Massed Compute publishes Agent Skills — markdown workflow templates for common operations like GPU selection and cost auditing. Full docs at vm-docs.massedcompute.com/docs/category/mcp.

Installation

Step 1. Get your API key

Open vm.massedcompute.com/settings/api, create a key (read-only for analysis-only assistants; full-access to allow launch / restart / terminate / SSH-key changes), copy it.

Step 2. Pick an install path

Hosted endpoint — point your client at the streamable-HTTP URL, zero install
Local CLI — runs on your machine, key stored in your OS config dir

Hosted endpoint

Same 14 tools, same API key, nothing to install. Pick the snippet for your client:

Claude Code

bash

claude mcp add --transport http massed-compute \
  https://vm.massedcompute.com/api/mcp \
  --header "Authorization: Bearer MC_TOKEN"

Cursor — ~/.cursor/mcp.json

json

{
  "mcpServers": {
    "massed-compute": {
      "url": "https://vm.massedcompute.com/api/mcp",
      "headers": { "Authorization": "Bearer MC_TOKEN" }
    }
  }
}

Codex — ~/.codex/config.toml

toml

[mcp_servers.massed-compute]
url = "https://vm.massedcompute.com/api/mcp"
bearer_token_env_var = "MC_TOKEN"
enabled = true

Claude Desktop

Claude Desktop does not yet speak streamable-HTTP MCP, so use mcp-remote as a stdio↔HTTP bridge. Config at ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

json

{
  "mcpServers": {
    "massed-compute": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://vm.massedcompute.com/api/mcp",
        "--header", "Authorization: Bearer MC_TOKEN"
      ]
    }
  }
}

Local CLI

Install via whichever ecosystem you prefer:

bash

npm install -g massed-compute-mcp     # Node >= 20
# or
pip install massed-compute-mcp        # Python >= 3.10
# or
uv tool install massed-compute-mcp    # fast Python install via uv

Run one-shot setup:

bash

massed-compute-mcp init

init prompts for the key, validates it upstream, stores it at 0600 (POSIX), detects installed MCP clients (Claude Code, Cursor, Claude Desktop, Codex), and offers to wire each one. A timestamped backup is taken before any client edit. Restart wired clients to pick up the tools.

Config file location:

Linux: $XDG_CONFIG_HOME/massed-compute/config.json (falls back to ~/.config/...)
macOS: ~/Library/Application Support/massed-compute/config.json
Windows: %APPDATA%\massed-compute\config.json

Non-interactive (CI / scripts):

bash

# Key from env, auto-wire every detected client
MASSED_COMPUTE_API_KEY=<your-key> massed-compute-mcp init --yes

# Key from a file, wire only specific clients
massed-compute-mcp init --token-file ~/keys/mc --yes --clients claude-code,cursor

# Store the key only; don't touch any client config
massed-compute-mcp init --yes --no-install-clients

Add or remove a client later:

bash

massed-compute-mcp install-client cursor       # claude-desktop | codex | claude-code
massed-compute-mcp uninstall-client cursor

install-client is idempotent — re-running when the entry already matches is a silent no-op.

Verifying the connection

bash

massed-compute-mcp doctor

doctor confirms the stored key still works, prints the tool catalog, and shows copy-pasteable snippets for any clients you didn't auto-wire. Or just ask your assistant "Validate my Massed Compute API key." — a { message: "Valid Token" } response confirms the wiring.

CLI reference

Command	What it does
`massed-compute-mcp` (no args)	Run the MCP server over stdio
`massed-compute-mcp init`	First-run setup: prompt, validate, store, wire clients
`massed-compute-mcp doctor`	Verify the stored key and print client snippets
`massed-compute-mcp install-client <id>`	Wire a single client (`claude-code`, `cursor`, `claude-desktop`, `codex`)
`massed-compute-mcp uninstall-client <id>`	Remove our entry from a client config
`massed-compute-mcp config show`	Print resolved config path, masked key, resolution chain
`massed-compute-mcp logout`	Delete the stored API key
`massed-compute-mcp tools [--json]`	Print the tool catalog (no upstream call)
`massed-compute-mcp version`	Print the version

Key resolution

When the server starts, the API key is taken from the first source that provides one:

--token <value> CLI flag
--token-file <path> CLI flag (first line, trimmed)
MASSED_COMPUTE_API_KEY environment variable
Stored config file written by init

If none of those are set, the server exits non-zero with a pointer to massed-compute-mcp init. Override the upstream with MASSED_COMPUTE_API_BASE_URL (default https://vm.massedcompute.com).

Resources

License

MIT — see LICENSE.

Install

Configuration

Environment variables

MASSED_COMPUTE_API_KEYsecret

Your Massed Compute API key (Bearer token). Generate at https://vm.massedcompute.com/settings/api. Optional — `massed-compute-mcp init` provides an interactive first-run flow that prompts for the key, validates it, and stores it locally with 0600 permissions.

claude_desktop_config.json

{
  "mcpServers": {
    "mcp": {
      "command": "npx",
      "args": [
        "-y",
        "massed-compute-mcp@1.0.2"
      ],
      "env": {
        "MASSED_COMPUTE_API_KEY": "<YOUR_MASSED_COMPUTE_API_KEY>"
      }
    }
  }
}

gpu_inventory_list

images_list

instances_list

instances_get

instances_launch

instances_restart

instances_terminate

coupon_information

coupon_accepted_products

account_token_validation

account_billing

ssh_keys_list

ssh_keys_create

ssh_keys_delete

recipes_list

recipes_search

recipes_get

Massed Compute MCP Server

Contents

Overview

Installation

Step 1. Get your API key

Step 2. Pick an install path

Hosted endpoint

Local CLI

Verifying the connection

CLI reference

Key resolution

Resources

License

Install

Configuration