blofin-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BLOFIN_API_KEY | Yes | Your BloFin API key | |
| BLOFIN_BASE_URL | No | API base URL (defaults to demo trading) | https://demo-trading-openapi.blofin.com |
| BLOFIN_API_SECRET | Yes | Your BloFin API secret | |
| BLOFIN_PASSPHRASE | Yes | Your BloFin API passphrase |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_instrumentsA | Get available trading instruments. Returns contract specifications including min size, tick size, leverage limits. |
| get_tickersA | Get latest price snapshot, best bid/ask, and 24h trading volume for instruments. |
| get_orderbookA | Get order book depth for an instrument. |
| get_tradesB | Get recent trades for an instrument. |
| get_mark_priceB | Get mark price and index price for instruments. |
| get_candlesticksC | Get candlestick/kline data for an instrument. |
| get_funding_rateB | Get current funding rate for instruments. |
| get_funding_rate_historyB | Get historical funding rate data. |
| get_balanceA | Get futures account balance details including equity, available balance, frozen amounts. |
| get_positionsC | Get current open positions. |
| get_leverage_infoB | Get leverage info for an instrument. |
| set_leverageB | Set leverage for an instrument. |
| get_margin_modeA | Get current account-level margin mode (cross or isolated). |
| set_margin_modeC | Set account-level margin mode. |
| get_position_modeA | Get current position mode (long_short_mode or net_mode). |
| set_position_modeC | Set position mode. |
| get_account_configA | Get account configuration including position mode, account level, etc. |
| place_orderC | Place a new futures order. Supports limit, market, post_only, fok, ioc order types. |
| cancel_orderC | Cancel an existing order. |
| batch_ordersA | Place multiple orders at once (up to 20). All must share same instId and marginMode. |
| cancel_batch_ordersB | Cancel multiple orders at once. |
| close_positionC | Close a position for an instrument via a market order. |
| get_open_ordersC | Get list of currently open/pending orders. |
| get_order_historyC | Get order history. |
| get_order_detailA | Get details of a specific order. Either orderId or clientOrderId or algoClientOrderId is required. |
| get_fills_historyC | Get trade fill history for futures. |
| place_tpslB | Place take-profit/stop-loss order for a position. Either tpTriggerPrice or slTriggerPrice (or both) must be provided. |
| cancel_tpslB | Cancel take-profit/stop-loss orders. Accepts a JSON array of cancel objects. |
| get_pending_tpslB | Get pending take-profit/stop-loss orders. |
| get_tpsl_historyB | Get take-profit/stop-loss order history. |
| place_algo_orderC | Place an algo order (trigger order). |
| cancel_algo_orderB | Cancel an algo order. |
| get_pending_algo_ordersC | Get pending algo orders. |
| get_algo_order_historyC | Get algo order history. |
| get_asset_balancesC | Get asset balances across different account types (funding, futures, etc.). |
| fund_transferB | Transfer funds between accounts (funding, futures, copy_trading, earn, spot, inverse_contract). |
| get_fund_transfer_historyB | Get fund transfer history between accounts. |
| get_deposit_historyC | Get deposit history. |
| get_withdrawal_historyC | Get withdrawal history. |
| get_apikey_infoA | Get API key information including permissions, IP whitelist, and expiration. |
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 40 tools
Each tool targets a distinct resource or action, with clear separation between data retrieval (get_*), order placement (place_*), cancellation (cancel_*), and configuration (set_*). Even within similar categories like cancellations, the tool descriptions specify different order types or modes, avoiding ambiguity.
Most tools follow a consistent verb_noun pattern with underscores (e.g., get_balance, place_order). Minor deviations like 'batch_orders' (noun phrase as command) and 'fund_transfer' (two nouns) are present, but the overall pattern is predictable and readable.
With 40 tools, the set is comprehensive for a crypto exchange API covering orders, positions, account, market data, and transfers. While it is on the higher end, each tool serves a distinct purpose and is justified by the complexity of the domain.
The tool surface covers full lifecycle operations for orders (place, cancel, query), positions (close, leverage, margin mode), account configuration, market data (orderbook, candlesticks, tickers), transfers, and history. No obvious gaps are present for a typical futures trading workflow.