Massed Compute Mcp

Name: Massed Compute Mcp
Author: Massed-Compute

@Massed-Compute

About Massed Compute Mcp

Model Context Protocol server for Massed Compute — list GPU inventory, launch and manage VM instances, manage SSH keys, audit billing.

#gpu #cloud #infrastructure #devop

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

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

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Massed Compute MCP?

A Model Context Protocol (MCP) 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, and audit billing.

How to use Massed Compute MCP?

Obtain an API key from your Massed Compute settings (read-only for analysis-only assistants, full-access for destructive operations). Then either use the hosted endpoint by pointing your client at the streamable HTTP URL, or install the CLI locally via npm install -g massed-compute-mcp (or pip/uv) and run massed-compute-mcp init to store your key and automatically wire detected clients.

Key features of Massed Compute MCP

14 tools mapping 1:1 to documented API endpoints
Read-only and full-access key separation
Hosted endpoint (zero install) or local CLI
Automatic client wiring for Claude, Cursor, Codex, Claude Desktop
GPU inventory, VM management, SSH keys, billing, and coupons
Doctor command to verify connection and print tool catalog

Use cases of Massed Compute MCP

Launch and manage GPU instances via natural language in an AI assistant
Check GPU inventory, pricing, and regional capacity before purchasing
Audit billing settings and apply coupon discounts
Manage SSH keys and automate VM lifecycle (restart, terminate)
Validate API tokens and retrieve account information

FAQ from Massed Compute MCP

What type of API key is required?

Read-only keys allow analysis-only tools (list, get, billing, coupons); full-access keys are required for tools that launch, restart, terminate, or modify SSH keys. Destructive tools are hidden from the catalog when a read-only key is used.

How do I install the server locally?

Install via npm install -g massed-compute-mcp (Node >= 20), pip install massed-compute-mcp (Python >= 3.10), or uv tool install massed-compute-mcp. Then run massed-compute-mcp init to set up your API key and wire clients.

How do I configure clients to use the hosted endpoint?

Use the client-specific snippets provided in the README: for Claude Code use claude mcp add, for Cursor add to ~/.cursor/mcp.json, for Codex add to ~/.codex/config.toml, and for Claude Desktop use the mcp-remote bridge.

How can I verify the connection is working?

Run massed-compute-mcp doctor to confirm the stored key, see the tool catalog, and get copy-pasteable client snippets. Alternatively, ask your assistant "Validate my Massed Compute API key."

How is the API key resolved when the server starts?

The key is taken from the first available source: --token CLI flag, --token-file CLI flag, MASSED_COMPUTE_API_KEY environment variable, or the stored config file written by init. If none are set, the server exits with a pointer to the init command.