An agent that can place a leveraged futures position is exactly as dangerous as it sounds. The project ships the right controls: paper trading for rehearsal, and a read-only startup flag that deletes the write tools rather than merely discouraging them. Decide which one you are in before you connect it, not after.
The entry point to a set of packages rather than a single server: an MCP server for desktop assistants, a CLI plus skills for terminal agents, a market-signal package that needs no account, an SDK, and an installer that sets up and upgrades them together.
- 89 Bitget UTA v3 operations, presented through 14 curated intent verbs rather than raw endpoints
- Spot orders, futures positions with leverage, internal fund transfers, batch cancels and an account overview
- Market analysis skills that need no account or API key - macro, on-chain intel, sentiment, technicals and a daily briefing
- Two meta tools, discover and raw, for exploring the operation surface and calling any operation by its ID
- A paper-trading mode for rehearsing before real funds are involved
- A read-only switch that removes every write tool at startup
Node.js 20 or higher. A Bitget API key from the exchange's API management page for anything that touches your account; the market-signal package needs neither an account nor a key. The installer wires the packages into Claude Code, Codex and OpenClaw for terminal agents, while desktop assistants use the MCP package instead. The tools deliberately do not read .env files, so credentials must be passed the way each package documents.
One command plus a key — npx -y @bitget-ai/bitget-agent-mcp, then supply credentials