Connect your agent to Gambit

Endpoints

• MCP: https://api.gambit.trading/mcp
• REST: https://api.gambit.trading
• OAuth metadata: https://api.gambit.trading/.well-known/oauth-authorization-server
• Server card: https://api.gambit.trading/mcp/server.json
• Machine docs: https://gambit.trading/llms.txt

Connect: sign in with OAuth

Add the URL to your client. It opens Gambit in the browser; you sign in and choose the scopes to grant. No key to copy or paste.

• Claude Code

  Add the server, then run /mcp inside Claude Code, pick gambit, and sign in in the browser.

  claude mcp add --transport http gambit https://api.gambit.trading/mcp

  Claude Code docs · checked 2026-10-08

• Claude (web and desktop)

  Customize → Connectors → + Add → Add custom connector. Name it Gambit, paste the URL, continue, and sign in when prompted. Turn it on per chat from the + menu → Connectors. On Team and Enterprise, an owner adds it first under Organization settings → Connectors; members then click Connect.

  Claude (web and desktop) docs · checked 2026-10-08

• ChatGPT

  Open chatgpt.com/plugins → + → Add custom MCP server. Paste the URL as the public endpoint, keep the discovered authentication, and select Create as a plugin; sign in when prompted. Availability depends on your plan and workspace policy.

  ChatGPT docs · checked 2026-10-08

• Codex CLI

  Add the server, then log in. The login opens the browser to sign in.

  codex mcp add gambit --url https://api.gambit.trading/mcp
  codex mcp login gambit

  Codex CLI docs · checked 2026-10-08

• Cursor

  Add this to ~/.cursor/mcp.json (or .cursor/mcp.json in a project). Cursor prompts you to sign in.

  { "mcpServers": { "gambit": { "url": "https://api.gambit.trading/mcp" } } }

  Cursor docs · checked 2026-10-08

• VS Code

  Add this to .vscode/mcp.json (or run MCP: Open User Configuration). Start the server and sign in when VS Code prompts.

  { "servers": { "gambit": { "type": "http", "url": "https://api.gambit.trading/mcp" } } }

  VS Code docs · checked 2026-10-08

• Any other MCP client

  If it supports remote (Streamable HTTP) servers with OAuth, the URL is all it needs.

  Any other MCP client docs · checked 2026-10-08

A grant that includes api:trade is a live trading credential, the same as an api:trade key.

Headless agents and scripts: API key

No browser at sign-in time? Create a key in Settings → API, then:

read -rs GAMBIT_API_KEY && export GAMBIT_API_KEY
claude mcp add --transport http gambit https://api.gambit.trading/mcp \
  --header 'Authorization: Bearer ${GAMBIT_API_KEY}'

Any client that accepts a custom header works the same way, and /llms.txt shows how to call the endpoint as plain JSON. Supply the key via a silent local prompt or a secret manager. Never paste it into chat.

Scopes

api:read is market data, opportunities, Hyperliquid balances, positions, orders, and recommendations. Brokerage holdings need api:portfolio. api:trade is the only scope that can place a trade, and only from the agent wallet, via propose then confirm after the client shows the preview to a human. Keys and grants without that scope cannot trade.