mcp-mercado-bitcoin
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MB_API_KEY | Yes | Client ID (Chave de API) do Mercado Bitcoin | |
| MB_DRY_RUN | No | Modo simulação (não executa operações reais) | false |
| MB_API_SECRET | Yes | Client Secret (Segredo da API) do Mercado Bitcoin | |
| MB_AUTO_CONFIRM | No | Pular confirmação em operações perigosas | false |
| MB_MAX_ORDER_BRL | No | Valor máximo por ordem (em BRL) | |
| MB_OPERATION_MODE | No | Modo de operação: readonly, trading ou full | trading |
| MB_DAILY_LIMIT_BRL | No | Limite diário de negociação (em BRL) |
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 |
|---|---|
| mb_statusA | Check the current configuration and health of the Mercado Bitcoin MCP server. Shows operation mode, security limits, authentication status and daily spending. |
| mb_get_orderbookA | Get the order book (asks and bids) for a trading pair on Mercado Bitcoin. Returns current buy and sell orders with prices and quantities. |
| mb_get_tradesA | Get recent executed trades for a trading pair. Useful for seeing market activity, recent prices and volumes. |
| mb_get_symbolsA | List available trading symbols/pairs on Mercado Bitcoin with metadata (min/max price, min/max volume, asset type). Without a filter, returns only BRL pairs (most common) in pages of 200. Use 'symbols' for specific pairs or 'offset' to paginate through all available pairs. Mercado Bitcoin has 1900+ symbols including crypto, fan tokens, DeFi, and tokenized assets. |
| mb_get_tickersA | Get current price tickers for one or more trading pairs. Returns: last price, bid, ask, high, low, open, and 24h volume. |
| mb_get_candlesA | Get OHLCV candlestick data for charting and technical analysis. Resolutions: 1m, 15m, 1h, 3h, 1d, 1w, 1M. |
| mb_get_asset_feesA | Get deposit and withdrawal fees for a specific asset. Includes minimum amounts and confirmation requirements per network. |
| mb_get_asset_networksA | List available blockchain networks for a specific asset. Important for multi-network assets like USDT (Ethereum, Stellar, etc.). |
| mb_list_accountsA | List all your Mercado Bitcoin accounts (wallets). Returns account IDs, names, currency and type. You need the accountId for most other operations. |
| mb_get_balancesA | Get asset balances for an account. Shows available, on_hold (in open orders), and total for each asset. By default, only returns assets with balance > 0 (most common use case). Set hide_zero=false to include all 1900+ assets. |
| mb_get_tierB | Get the fee tier level of an account. Higher tiers have lower trading fees. |
| mb_get_trading_feesA | Get maker and taker fee rates for a specific market. Useful before placing orders to estimate costs. |
| mb_get_positionsA | List open positions with average entry price, quantity and side. Useful for portfolio analysis and P&L tracking. |
| mb_internal_transferA | Transfer an asset between your own Mercado Bitcoin accounts (sub-wallets). Requires confirmation. Call first with confirm=false to preview, then confirm=true to execute. |
| mb_place_orderA | Place a buy or sell order on Mercado Bitcoin. Supports market, limit, stoplimit and post-only orders. IMPORTANT: This tool uses a two-step confirmation flow for safety.
For market buy orders, you can use 'cost' (value in BRL, e.g. 'buy R$500 of BTC') instead of 'qty'. The MCP will automatically calculate the quantity based on the current market price. Order types:
|
| mb_list_ordersA | List orders for a specific trading pair. Filter by status, side, date range. Returns order details including executions (fills). |
| mb_get_orderA | Get detailed information about a specific order, including all executions (fills), average price, fees and timestamps. |
| mb_cancel_orderA | Cancel a specific open order. Requires confirmation. Call with confirm=false first to preview, then confirm=true to execute. |
| mb_cancel_all_ordersA | Cancel ALL open orders on your account. Optionally filter by symbol. DANGEROUS: This cancels multiple orders at once. Requires confirmation. Call with confirm=false first to preview, then confirm=true to execute. |
| mb_list_all_ordersA | List orders across ALL trading pairs for an account. Useful for getting a complete picture of trading activity. |
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 20 tools
Each tool targets a distinct resource and operation: market data (orderbook, trades, tickers, candles, symbols), account info (accounts, balances, tier, fees, positions), and order management (place, list, get, cancel, cancel all, list all). There is no overlapping purpose; even similar tools like list_orders vs list_all_orders are clearly distinguished by scope.
Most tools follow an mb_<verb>_<noun> pattern (get, list, place, cancel), but there are minor deviations: mb_status uses a noun without a verb, mb_internal_transfer uses an adjective-noun construction, and get vs list is used inconsistently for collection-returning tools (e.g., mb_get_trades vs mb_list_orders). Overall the prefix mb_ and predictable object names keep it readable.
With 20 tools, this is a substantial surface that could be trimmed by combining related functions (e.g., fees/networks, order listing variants). However, the tools are all meaningful and cover a full exchange API, fitting the 16-25 'heavy' range where some consolidation would help.
The toolset covers the core lifecycle for trading: market data, account balances, order placement/retrieval/cancellation, and internal transfers. The main gap is external deposit/withdrawal operations, though fee and network information exists, and users cannot move funds in/out of the exchange directly.