Labsco
MCP SERVER

Massed Compute MCP

by Massed-Compute ↗

Browse GPU inventory, launch and manage VMs, and audit billing on a Massed Compute account.

Cloud Resources & Infrastructure as Code
Summary
The key you issue decides what the assistant can do, and the server is what enforces it.

A read-only key means a destructive call is refused by the endpoint rather than avoided by a prompt, and the same rule applies to every client. Because the local package proxies the hosted catalog verbatim, what you install today still matches what the service offers next month.

What it is

A client for Massed Compute's GPU cloud. The published packages are a verbatim proxy of the hosted endpoint — every JSON-RPC message is forwarded unchanged with your key attached — so the tool catalog, the schemas and the security rules all come from the live service rather than from a local copy that can go stale.

What you get
  • GPU inventory browsed with pricing and capacity, and the VM image catalog beside it
  • Instances launched, restarted and terminated, with SSH keys managed alongside them
  • Coupons and billing audited from the same connection
  • Setup recipes served by the endpoint, so new capabilities appear without updating anything locally
  • Scope enforced where it cannot be argued with: issue a read-only key and the endpoint rejects launch, restart, terminate and SSH-key changes at call time, with credential redaction handled server-side for every client identically
  • The live catalog printable from the command line, so what the assistant can reach is checkable before you wire it up
  • Agent Skills published alongside the tools as markdown workflow templates for jobs like GPU selection and cost auditing
Requirements

A Massed Compute account and an API key from the settings page — read-only for an analysis-only assistant, full access to allow launch, restart, terminate and SSH-key changes. Nothing to install if your client speaks streamable HTTP: point it at https://vm.massedcompute.com/api/mcp with the key as a bearer token, or bridge through mcp-remote for clients that do not. The local CLI installs from npm on Node 20 or newer, or from PyPI on Python 3.10 or newer; its init command prompts for the key, validates it upstream, stores it with 0600 permissions on POSIX, detects installed clients and offers to wire each one after taking a timestamped backup. The key is resolved from a flag, a token file, MASSED_COMPUTE_API_KEY, then the stored config, in that order.

Setup effort

One command plus a key — npm install -g massed-compute-mcp, then supply credentials