Set up your client
Endpoint: https://vm.massedcompute.com/api/mcp
Auth: Authorization: Bearer <token>
Two ways to authenticate:
- API token — paste a Bearer token into the client config. Snippets below use
MC_TOKENas a placeholder; replace it with the API token from API Settings. Restart the client after saving (full quit and reopen for Codex / Claude Desktop). - OAuth — some MCP clients (Claude, Codex, ChatGPT) discover OAuth from
https://vm.massedcompute.com/api/mcpwhen no token is sent. Sign in, approve full or read-only, then manage the grant under Connected Apps.
Use the tabs for the API-token path. Setup images are schematic illustrations; menu names and layout may vary by client version.
Create a read-only key if the assistant only needs to inspect inventory, billing, and instances. Create a full-access key if it needs to launch, restart, terminate, or manage SSH keys.
- Claude Code
- Cursor
- Codex
- Claude Desktop
The fastest path is the CLI:
claude mcp add --transport http massed-compute \
https://vm.massedcompute.com/api/mcp \
--header "Authorization: Bearer MC_TOKEN"
This registers the server globally. Run claude from any project and ask "list my Massed Compute instances" — Claude Code discovers and calls the tools automatically.
To configure by hand instead, edit ~/.claude.json (global) or .mcp.json in a project root:
{
"mcpServers": {
"massed-compute": {
"type": "http",
"url": "https://vm.massedcompute.com/api/mcp",
"headers": {
"Authorization": "Bearer MC_TOKEN"
}
}
}
}
Useful commands: claude mcp list shows registered servers, claude mcp remove massed-compute uninstalls, and claude --debug traces tool list/call activity if something looks off.
1. Open settings
Open Settings → Cursor Settings → Tools & MCPs.

2. Add the server config
Edit ~/.cursor/mcp.json (global) or .cursor/mcp.json in a project. Cursor watches both:
{
"mcpServers": {
"massed-compute": {
"url": "https://vm.massedcompute.com/api/mcp",
"headers": {
"Authorization": "Bearer MC_TOKEN"
}
}
}
}

3. Confirm connected
The massed-compute server should show green with about 17 tools (fewer if you used a read-only key). Red usually means a bad token, invalid JSON, Cursor older than 0.45 (HTTP MCP), or a network block — hover the status for the error.

4. Try a real call
In chat, type @massed-compute to inline the tool list, or ask "Validate my Massed Compute API key" / "List my running VMs."
Put the key in an environment variable, not in config.toml. Codex / ChatGPT.app only see env vars inherited when the app launches. A shell-profile export is not inherited by an app opened from the Dock or Spotlight.
1. Open Connections
Open Settings → Connections (MCP / connections panel in Codex or ChatGPT.app).

2. Edit config and export the key
Edit ~/.codex/config.toml:
[mcp_servers.massed-compute]
url = "https://vm.massedcompute.com/api/mcp"
bearer_token_env_var = "MASSED_COMPUTE_API_KEY"
enabled = true
For the CLI, export in the same terminal before running codex:
export MASSED_COMPUTE_API_KEY=MC_TOKEN

3. Launch with the environment variable
For the macOS GUI, fully quit the app first, then launch its executable from the same terminal where you exported the variable:
/Applications/Codex.app/Contents/MacOS/Codex
If you use ChatGPT.app, run /Applications/ChatGPT.app/Contents/MacOS/ChatGPT instead (adjust the path if installed elsewhere). Reopening from the Dock or Spotlight does not inherit your shell export. A soft reload or an already-running app also keeps the old environment.
Alternatively, set the variable in the macOS GUI login environment with launchctl setenv MASSED_COMPUTE_API_KEY MC_TOKEN, then fully quit and reopen the app from the Dock. Replace MC_TOKEN with your key without sharing it in screenshots or command logs. This setting lasts for the login session; a shell-profile export alone does not provide it. To remove it, use launchctl unsetenv MASSED_COMPUTE_API_KEY.
4. Confirm tools
Check that massed-compute is enabled and tools appear via /tools (about 17 with a full-access key).

Claude Desktop speaks MCP over stdio, so use the mcp-remote bridge to reach the HTTP endpoint. A raw url field will not work.
1. Open settings
Open Settings → Developer.

2. Edit the config
Edit claude_desktop_config.json:
| OS | Path |
|---|---|
| macOS | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Windows | %APPDATA%\Claude\claude_desktop_config.json |
{
"mcpServers": {
"massed-compute": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://vm.massedcompute.com/api/mcp",
"--header",
"Authorization: Bearer MC_TOKEN"
]
}
}
}

3. Fully quit and reopen
Fully quit and reopen Claude Desktop after saving. Tools appear in the tool indicator (about 17 with a full-access key).

Example tool list and response
These are client-neutral illustrations rendered from synthetic data, not captures of Cursor, Codex, or Claude Desktop. Your client's layout will differ. All identifiers in the response are placeholders; no VM was launched to make this example.
Verify you're connected
Ask your assistant:
- "Validate my Massed Compute API key"
- "List my running Massed Compute VMs"
- "Search setup recipes for Jupyter"
If it returns real account data (or a recipe list), you're wired up. If not, see Troubleshooting.
What's next
- Tools reference — all 17 tools with example prompts
- Agent Skills — downloadable workflows for GPU pick, launch, cost, and safe terminate
- Troubleshooting — common failures and fixes