MCP Bitget Trading Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| getPriceB | Get current price for a trading pair (spot or futures) |
| getTickerB | Get full ticker information for a trading pair |
| getOrderBookC | Get order book (market depth) for a trading pair |
| getCandlesC | Get historical candlestick/OHLCV data |
| getBalanceC | Get account balance information |
| placeOrderC | Place a new buy or sell order (automatically detects spot vs futures) |
| cancelOrderC | Cancel an existing order |
| getOrdersC | Get current open orders |
| getPositionsC | Get current futures positions |
| setLeverageC | Set leverage for futures trading |
| getMarginInfoC | Get margin account information |
| connectWebSocketB | Connect to WebSocket for real-time data |
| disconnectWebSocketB | Disconnect from WebSocket |
| subscribeToTickerC | Subscribe to real-time ticker updates |
| subscribeToOrderBookC | Subscribe to real-time order book updates |
| unsubscribeFromChannelC | Unsubscribe from a WebSocket channel |
| getWebSocketStatusB | Get WebSocket connection status |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 17 tools
Each tool has a distinct purpose with clear boundaries: order management (cancelOrder, placeOrder, getOrders), account data (getBalance, getMarginInfo, getPositions), market data (getCandles, getOrderBook, getPrice, getTicker), and WebSocket operations (connectWebSocket, disconnectWebSocket, subscribeToOrderBook, subscribeToTicker, unsubscribeFromChannel, getWebSocketStatus). There is no overlap or ambiguity between tools.
All tool names follow a consistent camelCase verbNoun pattern (e.g., cancelOrder, getBalance, subscribeToOrderBook). The naming is uniform across the entire set, making it predictable and easy to understand.
With 17 tools, the count is well-suited for a trading server covering order execution, account management, market data, and real-time WebSocket functionality. Each tool serves a specific and necessary role without redundancy, fitting within the typical 3-15 range for such a domain.
The tool set provides comprehensive coverage for cryptocurrency trading: full CRUD for orders (place, cancel, get), account data (balance, margin, positions), market data (historical and real-time via WebSocket), and futures-specific operations (leverage setting). There are no obvious gaps, enabling agents to handle complete trading workflows.