MCP.so
ログイン

Massed Compute MCP Server

@Massed-Compute

基本情報

カテゴリ

開発者ツール

ライセンス

MIT

トランスポート

stdio

作者

Massed-Compute

投稿者

TJ Frevert

Massed Compute MCP Server について

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

Massed Compute MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

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

Massed Compute MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

上のボタンでサーバーのエンドポイントに接続し、ツール一覧を取得できます。

概要

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

よくある質問

1

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.

2

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.

3

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.

4

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."

5

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.

コメント

「開発者ツール」の他のコンテンツ