Best for
- Users already running Hummingbot API who want AI-client control of trading
- Crypto traders comfortable with Docker/uv configuration
H
Hummingbot MCP Server
Official
Connect Hummingbot via MCP for automated multi-exchange crypto trading
GitHub source repository ↗
51FMRS · D
An officially maintained MCP server from Hummingbot that connects Claude and Gemini CLI over stdio to accounts, orders, positions, market data, and bot management tools. Well documented with uv and Docker paths and clear error messages, but only suitable for users who already run Hummingbot infrastructure.
Hummingbot MCP Server is a Model Context Protocol server that enables Claude and Gemini CLI to interact with the Hummingbot API for automated cryptocurrency trading across multiple exchanges. Maintained by Hummingbot, it exposes tools for account management, order and position handling, market data, funding rates, bot deployment, and controller configuration. It runs via uv locally or Docker, and can be deployed alongside the Hummingbot API using Docker Compose.
Tools
configure_server
View or update the active Hummingbot API server connection (host, port, credentials); the client automatically reconnects and config persists in ~/.hummingbot_mcp/server.yml
Setup
1) uv: install uv, clone https://github.com/hummingbot/mcp, run uv sync, copy .env.example to .env with HUMMINGBOT_API_URL, HUMMINGBOT_USERNAME, HUMMINGBOT_PASSWORD, then configure the client to run main.py via uv. 2) Docker: create .env, pull hummingbot/hummingbot-mcp:latest, use --network host on Linux or set the API URL to http://host.docker.internal:8000 on Mac/Windows, then configure a docker run command in the client. Alternatively deploy with Docker Compose alongside hummingbot-api, emqx, and postgres. Requires Python 3.11+ and a running Hummingbot API.
claude_desktop_config.json
{"mcpServers":{"hummingbot-mcp":{"type":"stdio","command":"uv","args":["--directory","/path/to/mcp","run","main.py"]}}}
Fit and risk
Not for
- Users without Hummingbot or a running API server
- Beginners without trading background who cannot absorb automated-trading risk
Required permissions
- Requires Hummingbot API username and password (HUMMINGBOT_USERNAME, HUMMINGBOT_PASSWORD)
- Requires a reachable Hummingbot API URL (HUMMINGBOT_API_URL)
- Docker deployment mounts ~/.hummingbot_mcp to persist configuration
Risks and side effects
- The server can place real trade orders; misconfiguration can lead to financial loss
- API credentials are stored in environment variables and .env files and must be protected
- Connecting to a wrong URL or exposing the API publicly introduces security risk
Troubleshooting
- On 'Cannot reach Hummingbot API', verify the API server is running and the URL is accessible
- Authentication failures (401) mean wrong credentials; use configure_server to update them
- On Mac/Windows Docker, use host.docker.internal instead of localhost
- On Linux Docker, add --network host to reach the host's API
Use cases
Place orders, manage positions, and check balances from Claude or Gemini CLI
Fetch market data such as prices, order books, candles, and funding rates
Deploy and manage Hummingbot bots and controller configuration
Deploy the MCP server together with Hummingbot API in the cloud via Docker Compose
Supported clients
Claude CodeFull support
Gemini CLIFull support