Gambit
LearnMCPDocs

Learn

Connect an agent to Gambit (MCP)

Gambit speaks MCP at https://api.gambit.trading/mcp over Streamable HTTP. Add that URL to Claude, ChatGPT, Claude Code, Codex, Cursor, or VS Code and sign in with OAuth; you choose the scopes on the consent page. Headless agents use a scoped API key instead. propose_trade and confirm_trade need api:trade and must show the preview to a human before confirm.

Updated 2026-10-08 · Gambit

Sign in with OAuth

Add https://api.gambit.trading/mcp as a remote MCP server. The client discovers Gambit’s OAuth 2.1 metadata from the 401 it gets back, registers itself, and opens gambit.trading/oauth/authorize. You sign in and tick the scopes to grant. No key is created, copied, or pasted.

Claude Code: claude mcp add --transport http gambit https://api.gambit.trading/mcp, then run /mcp and sign in. Claude on the web or desktop: Customize → Connectors → Add custom connector, paste the URL. ChatGPT: chatgpt.com/plugins → Add custom MCP server, paste the URL (depends on your plan and workspace policy). Codex CLI: codex mcp add gambit --url https://api.gambit.trading/mcp, then codex mcp login gambit. Cursor: add the URL under mcpServers in ~/.cursor/mcp.json. VS Code: add it as an http server in .vscode/mcp.json. Exact steps and config for each are on gambit.trading/mcp.

Headless agents: API key

For scripts, scheduled jobs, or an agent with no browser, create a scoped key at gambit.trading/settings/api and send it as a bearer header: claude mcp add --transport http gambit https://api.gambit.trading/mcp --header 'Authorization: Bearer ${GAMBIT_API_KEY}'. The same key works for plain-JSON calls to /mcp; /llms.txt has the recipe. Have the human supply the key via a silent local prompt or a secret manager. Never paste a key into chat.

What the tools do

Read tools return Hyperliquid market data, computed features, the Today’s Market opportunity feed, news, sentiment, and — with the right scopes — your positions, brokerage holdings, and recommendations. generate_recommendation and ask_gambit_agent spend quota. propose_trade stages a guardrailed preview and places nothing. confirm_trade executes it from the agent wallet only, after the client shows the preview.

What a connection can do

An OAuth grant and an API key follow the same rules: each does only what its scopes allow, and either one holding api:trade is a live trading credential. The server enforces guardrails and hourly caps; showing the preview to a human before confirm_trade is the client’s job. Grant api:trade only to a client you trust to do that.

Related: AI tools for Hyperliquid traders · Gambit FAQ — custody, confirms, and fees · What is a trade thesis card

Gambit
LearnMCPDocsllms.txtTermsPrivacyX
© All rights reserved