Chat assistants (MCP)
Run GPU jobs from a chat: connect supercomputer as an MCP server.
supercomputer is an MCP server. Add one URL to ChatGPT or any assistant that takes custom MCP connectors, and it can pick a GPU, start a job, watch its output and stop it, billed to your account by the second.
https://supercomputer.sh/mcpConnect
ChatGPT: Settings → Apps → enable Developer mode → Create → paste the URL with authentication set to OAuth → Connect.
Other assistants (web, desktop, mobile): Settings → Connectors → Add custom connector → paste the URL → Connect.
Either way a browser window opens: sign in with Google or email, add credits if the account is empty (any amount from $10; the card is saved for auto-refill), and click Allow. That is the whole setup; the connector stays signed in.
What the assistant can do
| Tool | What it does | Asks first? |
|---|---|---|
list_gpus | GPU types and current hourly prices | no |
get_balance | Who is signed in and the credit available | no |
run | Run a command or script to completion on a GPU | yes (spends money) |
get_job | State, cost so far and per-task result | no |
job_logs | The last lines of a job's output | no |
list_jobs | Recent jobs | no |
cancel_job | Stop a running or queued job | yes |
buy_credits | A checkout link to add prepaid credit | yes |
A run is a job: one command on a fresh machine with
the standard image (CUDA 12.8, PyTorch, the Hugging Face stack, vLLM), its
exit code and logs kept. Ask for a GPU by name (h100, 8x h100, l4,
cpu); the assistant resolves it against list_gpus.
Try: "Run nvidia-smi on an L4 and show me the output."
Notes
- Jobs are deduplicated by name: asking for the same name with the same command returns the existing job instead of starting a second one.
- Inline scripts are limited to 64 KB. For anything larger, give the assistant a command that clones a repo.
- Each account has one MCP key, named
mcp, separate from the dashboard and CLI keys. Revoke it from the dashboard to disconnect every assistant at once. - Server details: Streamable HTTP, protocol revision 2026-07-28, OAuth 2.1
with PKCE; clients register by Client ID Metadata Document or dynamic
registration. Metadata at
/.well-known/oauth-protected-resource/mcp.