io.github.Massed-Compute/mcp

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.

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

Restart one or more running VM instances by UUID.

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.

Look up information about a coupon by code.

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

Add a new SSH public key to the authenticated account.

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

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.

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.