thunder-cli AGENTS.md

Thunder Compute CLI

tnr is the CLI for Thunder Compute, a cloud GPU platform for AI/ML workloads.

MCP Server

Thunder Compute provides a remote MCP server that lets AI coding agents manage GPU instances directly — no local install required.

Connect it:

Agent	Setup
Claude Code	/mcp add --transport http https://www.thundercompute.com/mcp
Cursor	Add to .cursor/mcp.json (see config below)
Windsurf	Add to MCP settings (see config below)
Other agents	POST to endpoint with OAuth 2.0

{
  "mcpServers": {
    "thunder-compute": {
      "type": "http",
      "url": "https://www.thundercompute.com/mcp"
    }
  }
}

No API tokens needed — authenticates via OAuth in the browser.

37 tools: instance management, command execution and background jobs, file reads, GPU specs/pricing/availability, snapshots, SSH keys, port forwarding, billing, and API tokens.

Full MCP documentation

CLI Quick Reference

tnr login            # Authenticate with Thunder Compute
tnr create           # Create a GPU instance
tnr status           # List instances with status
tnr connect <id>     # SSH into an instance
tnr scp <src> <dst>  # Transfer files
tnr delete <id>      # Delete an instance
tnr port <id> <port> # Forward a port

Instance IDs are integers. Add --json for scripted/non-interactive usage.

Release Notes

Every pull request that changes cli/** must add a Changie fragment under cli/changes/unreleased/. The generated release-preparation pull request is the only exception because it consumes all pending fragments.

Use the fragment kind that matches the shipped user impact. Changie derives the SemVer bump automatically:

• Fixed, Changed, or Security: patch
• Added or Deprecated: minor
• Breaking or Removed: major
• Internal: no release bump

Example:

cd cli
changie new --kind Fixed \
  --body "Preserve the login link when the terminal is resized."