Infomaniak MCP Agent
Mogacode-maLABSCO 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
USE CASES
01
Finding the right GPU for a job
Browse the inventory with pricing and regional capacity, then look at the images available for the configuration you picked.
02
Standing up a machine and taking it down again
Launch the instance, restart it when it misbehaves, and terminate it when the work is finished — all needing a full-access key.
03
Letting an assistant analyse the account safely
Hand it a read-only key: browsing, billing and coupon questions all work, and the destructive calls are rejected at the endpoint.
04
Checking the wiring before you rely on it
Run the doctor command to confirm the stored key still works and print the live catalog, or ask the assistant to validate the key.
BEFORE YOU INSTALL
What to know first
Requires
- A Massed Compute API key, from vm.massedcompute.com/settings/api
- npx on PATH, only for Claude Desktop's mcp-remote bridge
INSTALLATION
Connect your client
Server setup
npm
TERMINAL
npm install -g massed-compute-mcpHosted endpoint
ENDPOINT URL
https://vm.massedcompute.com/api/mcpAdd this hosted endpoint to your MCP client using the credentials listed under Requirements.
MCP Clients
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add --transport http massed-compute \
https://vm.massedcompute.com/api/mcp \
--header "Authorization: Bearer <YOUR_MC_TOKEN>"<YOUR_MC_TOKEN> is your Massed Compute API key from vm.massedcompute.com/settings/api — a read-only key for an analysis-only assistant, full access to allow launch, restart, terminate and SSH-key changes.
Cursor
~/.cursor/mcp.json
CURSOR · JSON
{
"mcpServers": {
"massed-compute": {
"url": "https://vm.massedcompute.com/api/mcp",
"headers": {
"Authorization": "Bearer <YOUR_MC_TOKEN>"
}
}
}
}<YOUR_MC_TOKEN> is your Massed Compute API key from vm.massedcompute.com/settings/api — a read-only key for an analysis-only assistant, full access to allow launch, restart, terminate and SSH-key changes.
Claude Desktop
~/Library/Application Support/Claude/claude_desktop_config.json (macOS) · %APPDATA%\Claude\claude_desktop_config.json (Windows)
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"massed-compute": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://vm.massedcompute.com/api/mcp",
"--header",
"Authorization: Bearer <YOUR_MC_TOKEN>"
]
}
}
}<YOUR_MC_TOKEN> is your Massed Compute API key from vm.massedcompute.com/settings/api — a read-only key for an analysis-only assistant, full access to allow launch, restart, terminate and SSH-key changes. Claude Desktop reaches the hosted endpoint through the mcp-remote bridge, so npx must be on PATH.
Auto setup via CLI
AUTO SETUP VIA CLI · TERMINAL
massed-compute-mcp init
# or later: massed-compute-mcp install-client cursor # claude-desktop | codex | claude-codeNeeds the local CLI first (npm install -g massed-compute-mcp on Node 20+, or pip install massed-compute-mcp on Python 3.10+). init asks for your API key, checks it and stores it, then offers to wire each client it finds.
