Prerequisites
- A Thunder Compute account
- An AI agent that supports remote MCP servers (Claude Code, Cursor, Codex, etc.)
Setup
- Claude Code
- Codex
- Cursor
- Windsurf
- OpenCode
- Smithery
- Direct HTTP
Run this in your terminal:Then start Claude Code and run
/mcp to authenticate. A browser window will open for you to log in and authorize access.Manual setup
Manual setup
Alternatively, add to
~/.claude.json (global) or .claude.json in your project root:Authentication
No API tokens or environment variables needed. When you first connect, a browser window opens for you to log in with your Thunder Compute account and authorize access. Tokens refresh automatically, so you only authenticate once per session.Available Tools
Instance Management
Information
Snapshots
SSH Keys
Port Forwarding
Connectivity
Billing & Usage
API Tokens
Prompts
The MCP server includes built-in prompts that guide your agent through common multi-step workflows:Example Usage
Once configured, you can ask your AI agent things like:- “Spin up an A100 instance with PyTorch”
- “What GPU types are available and how much do they cost?”
- “Which GPUs are available right now?”
- “List my running instances”
- “Run
nvidia-smion my instance” - “Delete instance inst-abc123”
- “Forward port 8080 on my instance”
- “Create a snapshot of my instance before I make changes”
- “Deploy Llama 3 on a GPU”
- “How much have I spent this month?”
- “Show my invoice history”
- “Create an API token for my CI pipeline”
Troubleshooting
Authentication fails or browser doesn’t open: Run/mcp in Claude Code to manually trigger authentication. Make sure you’re logged in to your Thunder Compute account in the browser.
Browser callback fails after clicking Allow (common when running your AI agent inside a remote VM, container, or SSH session): if the browser shows a “can’t connect” / “site can’t be reached” page after consent, copy the full URL from the browser’s address bar (it looks like http://localhost:<port>/callback?code=...&state=...) and paste it into your AI agent where it prompts you to finish authentication. The agent will extract the code from the URL and complete the token exchange itself.
“Protected resource does not match” error: The URL in your MCP config must match the server’s configured resource URL exactly. Ensure you’re using https://www.thundercompute.com/mcp.
“token has invalid issuer” error: This is a server-side configuration issue. The MCP authentication client must be configured with the correct Stytch Connected Apps domain.
Tools not appearing: Restart your AI agent after changing MCP configuration. Most agents only read MCP config on startup.
MCP Directories
Thunder Compute is listed on major MCP directories for easy discovery:- Smithery — One-click install for supported clients
- MCP Registry — The official Model Context Protocol server registry
- Glama — Auto-indexed from the MCP Registry
- PulseMCP — Auto-indexed from the MCP Registry