Production-ready MCP server (v2.1.7) exposing 190+ Bybit V5 API tools — market data, trading, account management, WebSocket streams — to AI assistants like Claude, Cursor, VS Code via the Model Context Protocol. Built by Bybit, actively maintained with weekly releases. No API key needed for 22 market-data tools, supports both HMAC and RSA authentication, and instant npx startup. Distinguishes itself by being the official first-party MCP server (vs community wrappers) with comprehensive coverage including options, USDC contracts, and sub-account management.
npm install bybit-official-trading-serverNo compatibility data collected yet for this library.
Verified import paths — ran on the pinned version, not inferred.
Minimal configuration to connect Claude Desktop, Cursor, or VS Code to Bybit MCP server. Add your API key and secret, then test with a price query.
Remove BYBIT_API_SECRET when using RSA mode to avoid confusion. Set BYBIT_API_PRIVATE_KEY_PATH to absolute path of private key PEM file.
Implement client-side throttling or monitor 429 responses. Refer to Bybit API docs for rate limit tables.
Design your AI prompts to tolerate transient failures. Re-query if no data received within 10 seconds.
Upgrade Node.js to v20.6 or later. Check with `node --version`.
Use V5 endpoints only. If you have legacy V3 integrations, do not migrate to this MCP server expecting V3 compatibility.
Ensure Node.js >=20.6 is installed. Run `node --version` and `npx --version`. If missing, install via `npm install -g npx`.
Add BYBIT_API_KEY to your MCP client config env or use BYBIT_API_KEY=your_key npx ...` if running directly. Market-data tools do not need this.
If using RSA, ensure BYBIT_API_PRIVATE_KEY_PATH is set correctly. If using HMAC, set BYBIT_API_SECRET. Do not set both.
Validate JSON at jsonlint.com. Ensure structure: { "mcpServers": { "bybit": { ... } } }.