Reads work out of the box and cover both sides of the exchange — public market data and your own account. Order placement takes a deliberate act to turn on, and even then a notional cap and a dry-run path stand between an agent and an expensive mistake. Start on the testnet.
A Bybit API server for MCP clients. Market and account reads work immediately; every mutating call sits behind an explicit trading switch.
- Market data covering the order book, candlesticks, tickers, recent public trades, instrument metadata, funding rates, open interest, fee rates and server time through get_orderbook, get_kline, get_tickers, get_public_trade_history, get_instruments_info, get_funding_rate_history, get_open_interest, get_fee_rate and get_server_time
- market_snapshot returns the whole picture for one symbol in a single call, futures funding and open interest included
- Account reads: get_wallet_balance, get_positions, get_order_history, get_open_orders and get_api_key_information
- Order handling once trading is enabled: place_order, amend_order, cancel_order and cancel_all_orders, plus set_trading_stop, set_margin_mode and set_leverage
- validate_order runs pre-flight checks without placing anything and stays available whatever the trading switches say
- A hard read-only mode that overrides the trading switch, and a cap on the estimated notional value of a single order
- A testnet mode for experimenting, and a trimmed response mode for ticker and position payloads
Bybit API credentials: read permission for the data tools, wallet permission for balances, trade permission only if you enable order placement. Python from a checkout, or the published container image. Keys are passed through the environment and no tool returns them.
One command plus a key — npx -y @smithery/cli install @dlwjdtn535/mcp-bybit-server --client claude, then supply credentials