Bitget Agent MCP

What bitget-agent-mcp does

bitget-agent-mcp MCP server provides an MCP interface to Bitget’s Unified Trading Account API, allowing supported AI hosts to request market information and perform authenticated account operations. The implementation covers 89 UTA v3 operations across market data, spot and futures trading, account and fund management, sub-accounts, crypto loans, and tax-related functions.

The default interface uses a compact intent-oriented surface instead of exposing every API endpoint immediately. It includes 12 domain verbs plus discover and raw, for 14 tools by default. This keeps the initial tool set smaller while retaining access to the broader API.

How it works

An AI host launches the bitget-agent-mcp MCP server locally with npx and communicates with it over stdio. The server acts as a protocol adapter: it receives MCP tool calls, signs authenticated requests with HMAC-SHA256, sends them directly to Bitget’s official REST API, and returns the response to the host.

Agents can inspect the available surface in stages. They may list domains, inspect a verb, inspect an action’s input contract, and then execute the operation. Keyword search is available through discover, while raw can invoke a UTA v3 operation by its operationId.

Write protection is built into the tool layer. Any write can accept dryRun: true to preview a request. High-risk actions such as cancelling all orders or withdrawing require confirm: true; ordinary writes execute without that additional confirmation.

Setup and configuration

The bitget-agent-mcp MCP server requires Node.js 20 or newer and an MCP-capable host. The standard launch command is:

npx -y @bitget-ai/bitget-agent-mcp

Pass credentials through the host’s MCP configuration using BITGET_API_KEY, BITGET_SECRET_KEY, and BITGET_PASSPHRASE. The API key needs Read and Trade permissions for authenticated account and trading operations. Credentials are supplied through environment variables and, according to the project documentation, are not stored, logged, or proxied by the server.

Optional command-line modes include --read-only, which rejects writes, and --paper-trading, which sends signed requests to Bitget’s Demo Trading environment and requires a separate demo key. These modes cannot be used together. --modules limits loaded areas, with account,trade,market as the default; strategy, cryptoloans, and tax can be loaded on demand. --surface full exposes individual tools for the underlying v3 endpoints in addition to the default intent surface.

Tools and capabilities

Supported workflows include:

• Query current prices, funding rates, and historical OHLCV candles through market.
• Review balances and account information with account_overview.
• Place, inspect, and cancel orders through order.
• Configure leverage and manage positions with account and position actions.
• Move funds between Bitget accounts using transfer_funds.
• Access crypto loan operations through loan.
• Discover available domains, verbs, actions, and schemas with discover.
• Reach less common UTA v3 operations through raw.

Public market-data requests do not require API credentials. Requests that access or change account data do.

Limitations and notes

The server is intended for Bitget’s UTA v3 API and does not describe support for other exchanges. It runs as a local stdio process rather than a network listener or proxy. Trading, transfers, cancellations, withdrawals, and other account actions can have real consequences; --read-only, --paper-trading, and dryRun provide safer ways to inspect or rehearse workflows, but the documentation does not claim that every operation is simulated in every mode.