Use Tritonium from your AI agent

Claude Code

claude mcp add --transport http --scope user tritonium https://api.tritonium.com/mcp

Then run /mcp in Claude Code, choose tritonium and sign in. From a terminal, claude mcp login tritonium does the same. Over SSH, add --no-browser: open the link it prints on your own computer, and after you approve, paste the address your browser ends up on back into the terminal.

claude mcp add --transport http --scope user tritonium https://api.tritonium.com/mcp --header 'Authorization: Bearer ${TRITONIUM_API_KEY}'

Codex

codex mcp add tritonium --url https://api.tritonium.com/mcp

Codex notices that the server supports sign-in and opens your browser. It asks for every permission the server offers, so untick the ones your agent doesn't need before you approve. To sign in again later, run codex mcp login tritonium.

codex mcp add tritonium --url https://api.tritonium.com/mcp --bearer-token-env-var TRITONIUM_API_KEY

Cursor

Add this to .cursor/mcp.json in a project, or to ~/.cursor/mcp.json for all your projects. Then approve the server and sign in with the Cursor CLI:

{
  "mcpServers": {
    "tritonium": {
      "url": "https://api.tritonium.com/mcp"
    }
  }
}

cursor-agent mcp enable tritonium
cursor-agent mcp login tritonium

The Cursor CLI waits for your browser on http://localhost:8787/callback, so port 8787 must be free on the computer where it runs. Over SSH, forward that port with ssh -L 8787:localhost:8787 <host>; the Cursor CLI prints the same hint.

{
  "mcpServers": {
    "tritonium": {
      "url": "https://api.tritonium.com/mcp",
      "headers": { "Authorization": "Bearer ${env:TRITONIUM_API_KEY}" }
    }
  }
}

GitHub Copilot CLI

copilot mcp add --transport http tritonium https://api.tritonium.com/mcp

Then start copilot and run /mcp auth tritonium. Sign-in starts only in an interactive session, not with copilot -p. If Copilot still says the server requires authentication afterwards, restart copilot: it then uses the stored sign-in, also with copilot -p.

{
  "mcpServers": {
    "tritonium": {
      "type": "http",
      "url": "https://api.tritonium.com/mcp",
      "headers": { "Authorization": "Bearer ${TRITONIUM_API_KEY}" },
      "tools": ["*"]
    }
  }
}

Grok CLI

grok mcp add tritonium https://api.tritonium.com/mcp

Then start grok, open /mcps, select tritonium and press i to sign in.

[mcp_servers.tritonium]
url = "https://api.tritonium.com/mcp"
bearer_token_env_var = "TRITONIUM_API_KEY"

Antigravity

agy mcp add tritonium https://api.tritonium.com/mcp

Then start agy, open /mcp, choose tritonium and sign in. After you approve, your browser shows an Antigravity page with a code: paste that code into agy. The stored sign-in also works with agy --print.

{
  "mcpServers": {
    "tritonium": {
      "serverUrl": "https://api.tritonium.com/mcp",
      "headers": { "Authorization": "Bearer trtn_live_your_key" }
    }
  }
}

OpenClaw

openclaw mcp set tritonium '{"url":"https://api.tritonium.com/mcp","transport":"streamable-http","auth":"oauth"}'
openclaw mcp login tritonium

OpenClaw waits for your browser on http://127.0.0.1:8989/oauth/callback. If the browser cannot reach it, for example over SSH, finish with the openclaw mcp login tritonium --code <code> command that OpenClaw prints.

openclaw mcp set tritonium '{"url":"https://api.tritonium.com/mcp","transport":"streamable-http","headers":{"Authorization":"Bearer ${TRITONIUM_API_KEY}"}}'

Other MCP clients

Clients that support MCP authorization need only the URL https://api.tritonium.com/mcp. They find the sign-in on their own from the server's 401 response. The official MCP Python SDK's built-in OAuth support works without any Tritonium-specific settings.

Clients that cannot sign in can use an API key if they support remote Streamable HTTP servers with custom headers: send the header Authorization: Bearer <key>.