bybit-mcp-server

# bybit-mcp-server A [Model Context Protocol](https://modelcontextprotocol.io/) server for the [Bybit](https://bybit.com) V5 API. Connect AI assistants (Claude, Cursor, etc.) to Bybit for market data, trading, and account management — locally via stdio or remotely via HTTP with OAuth authentication. ## Quick Start ### Local (stdio) ```bash uvx bybit-mcp-server ``` ### Remote (Docker) ```bash docker pull ghcr.io/workspace/bybit-mcp-server:latest docker run -p 8000:8000 \ -e BYBIT_MCP_ADMIN_PASSWORD=your-password \ -e BYBIT_MCP_SECRET_KEY=$(python -c "from cryptography.fernet import Fernet; print(Fernet.generate_key().decode())") \ -e BYBIT_MCP_ISSUER_URL=https://your-server.example.com \ -v bybit-data:/app/data \ ghcr.io/workspace/bybit-mcp-server:latest ``` ## Transport Modes | Mode | Transport | Auth | Credentials | Use Case | |------|-----------|------|-------------|----------| | **Local** | `stdio` | None | Env vars | Claude Desktop, Cursor | | **Remote** | `streamable-http` | OAuth 2.0 | Web settings page | Claude Custom Connectors, shared servers | ## MCP Client Configuration ### Claude Desktop (Local) Add to `claude_desktop_config.json`: ```json { "mcpServers": { "bybit": { "command": "uvx", "args": ["bybit-mcp-server"], "env": { "BYBIT_API_KEY": "your-api-key", "BYBIT_API_SECRET": "your-api-secret", "BYBIT_TESTNET": "true" } } } } ``` ### Claude Custom Connectors (Remote) 1. Deploy the server with Docker (see [Deployment](#deployment)) 2. In Claude settings, add a Custom Connector: - **URL**: `https://your-server.example.com` 3. Claude handles OAuth automatically — you'll be prompted to log in with admin credentials 4. After connecting, visit `https://your-server.example.com/settings` to enter your Bybit API keys ### Cursor (Local) Add to `.cursor/mcp.json`: ```json { "mcpServers": { "bybit": { "command": "uvx", "args": ["bybit-mcp-server"], "en…