Bybit MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Enable debug logging | false |
| BYBIT_API_KEY | Yes | Your Bybit API key | |
| BYBIT_BASE_URL | No | Custom API base URL | |
| BYBIT_API_SECRET | Yes | Your Bybit API secret | |
| BYBIT_ENVIRONMENT | No | testnet or mainnet | testnet |
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 |
|---|---|
| get_priceC | Get the current price for a trading symbol |
| get_orderbookC | Get the order book depth for a trading symbol |
| get_klinesC | Get historical candlestick data for a trading symbol |
| get_24hr_tickerC | Get 24-hour trading statistics for symbols |
| get_account_infoB | Get account information and balances |
| get_wallet_balanceC | Get wallet balance for a specific account type |
| get_open_ordersC | Get list of open/active orders |
| get_order_historyC | Get historical orders |
| place_orderB | Place a new order (⚠️ WARNING: Can use real funds on mainnet) |
| cancel_orderC | Cancel an existing order (⚠️ WARNING: Affects real orders on mainnet) |
| cancel_all_ordersA | Cancel all orders for a symbol or category (⚠️ WARNING: Affects real orders on mainnet) |
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 11 tools
Every tool has a clearly distinct purpose with no ambiguity. Each targets a specific action on a distinct resource (e.g., cancel_all_orders vs. cancel_order, get_24hr_ticker vs. get_price, get_account_info vs. get_wallet_balance). The descriptions reinforce this clarity, making misselection unlikely.
All tools follow a consistent verb_noun pattern with snake_case throughout. The naming convention is predictable (e.g., get_*, cancel_*, place_order), making it easy for agents to understand and navigate the toolset without confusion.
With 11 tools, the count is well-scoped for a cryptocurrency exchange server. Each tool earns its place by covering essential trading operations (e.g., market data, order management, account info), avoiding bloat while providing comprehensive functionality.
The toolset offers complete CRUD/lifecycle coverage for trading on Bybit. It includes market data (get_price, get_klines, get_orderbook), order management (place_order, cancel_order, get_open_orders, get_order_history), account operations (get_account_info, get_wallet_balance), and auxiliary functions (cancel_all_orders, get_24hr_ticker), with no obvious gaps that would cause agent failures.