# mcp MCP server

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

## Links
- Registry page: https://www.getdrio.com/mcp/io-github-massed-compute-mcp
- Repository: https://github.com/Massed-Compute/massed-compute-mcp

## Install
- Command: `npx -y massed-compute-mcp`
- Endpoint: https://vm.massedcompute.com/api/mcp
- Auth: Auth required by registry metadata

## Setup notes
- Remote header: Authorization (required; secret)
- Package: Npm massed-compute-mcp v1.0.2
- Environment variable: MASSED_COMPUTE_API_KEY (secret)
- Package: Pypi massed-compute-mcp v1.0.2
- Environment variable: MASSED_COMPUTE_API_KEY (secret)
- The upstream registry signals required auth or secrets.
- Remote endpoint: https://vm.massedcompute.com/api/mcp
- Header: Authorization

## Tools
- gpu_inventory_list (List GPU inventory) - Retrieve the comprehensive list of available GPU configurations, their specs, pricing, and current capacity per region. Endpoint: https://vm.massedcompute.com/api/mcp
- images_list (List VM images) - Retrieve the catalog of preconfigured VM images available for deployment. Endpoint: https://vm.massedcompute.com/api/mcp
- instances_list (List running instances) - 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. Endpoint: https://vm.massedcompute.com/api/mcp
- instances_get (Get a running instance) - 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. Endpoint: https://vm.massedcompute.com/api/mcp
- instances_launch (Launch a new instance) - Deploy a new VM instance. Requires billing to be configured (recharge amount and threshold). This action incurs cost. Endpoint: https://vm.massedcompute.com/api/mcp
- instances_restart (Restart instances) - Restart one or more running VM instances by UUID. Endpoint: https://vm.massedcompute.com/api/mcp
- instances_terminate (Terminate instances) - 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. Endpoint: https://vm.massedcompute.com/api/mcp
- coupon_information (Get coupon information) - Look up information about a coupon by code. Endpoint: https://vm.massedcompute.com/api/mcp
- coupon_accepted_products (List products a coupon is valid for) - Look up which products a coupon code can be applied to, with current inventory availability. Endpoint: https://vm.massedcompute.com/api/mcp
- account_token_validation (Validate API token) - Confirm that the Bearer token used to call this MCP server is a valid Massed Compute user API key. Endpoint: https://vm.massedcompute.com/api/mcp
- account_billing (Get account billing snapshot) - Retrieve billing settings for the account, including billing method and recharge configuration. Endpoint: https://vm.massedcompute.com/api/mcp
- ssh_keys_list (List SSH keys) - List SSH keys associated with the authenticated account. Endpoint: https://vm.massedcompute.com/api/mcp
- ssh_keys_create (Add an SSH key) - Add a new SSH public key to the authenticated account. Endpoint: https://vm.massedcompute.com/api/mcp
- ssh_keys_delete (Delete an SSH key) - Remove an SSH key from the account. DESTRUCTIVE: any instances relying on this key may lose access. Confirm with the user before invoking. Endpoint: https://vm.massedcompute.com/api/mcp
- recipes_list (List setup recipes) - 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. Endpoint: https://vm.massedcompute.com/api/mcp
- recipes_search (Search setup recipes) - 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. Endpoint: https://vm.massedcompute.com/api/mcp
- recipes_get (Fetch a recipe by slug) - 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. Endpoint: https://vm.massedcompute.com/api/mcp

## Resources
Not captured

## Prompts
Not captured

## Metadata
- Owner: io.github.Massed-Compute
- Version: 1.0.2
- Runtime: Npm, Pypi
- Transports: STDIO, HTTP
- License: Not captured
- Language: Not captured
- Stars: Not captured
- Updated: May 19, 2026
- Source: https://registry.modelcontextprotocol.io