hyperliquid-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@hyperliquid-mcpshow me my open positions"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Hyperliquid MCP Server
A Model Context Protocol (MCP) server that provides comprehensive tools for interacting with the Hyperliquid decentralized exchange. This server enables AI assistants to perform trading operations, manage accounts, and retrieve market data through a standardized interface.
๐ Features
Account Management - Positions, balances, transfers, and leverage control
Order Management - Place, cancel, modify orders with advanced features
Market Data - Real-time prices, orderbooks, candles, and funding rates
Multiple Transports - stdio, HTTP (Streamable HTTP), and SSE support
Risk Management - Comprehensive validation and error handling
Type Safety - Full Pydantic validation for all inputs
Error Handling - Comprehensive error reporting and logging
๐ฆ Installation
Using uvx (Recommended)
# Run with stdio (default)
uvx hyperliquid-mcp
# Run with HTTP transport
uvx hyperliquid-mcp --transport http --port 3000
# Run with SSE transport
uvx hyperliquid-mcp --transport sse --port 3000Using uv
uv add hyperliquid-mcp
uv run hyperliquid-mcpUsing pip
pip install hyperliquid-mcp
hyperliquid-mcpCLI Options
hyperliquid-mcp [OPTIONS]
Options:
--transport, -t {stdio,http,sse} Transport type (default: stdio)
--host HOST Host to bind to (default: localhost)
--port, -p PORT Port to listen on (default: 3000)
--log-level, -l {debug,info,warn,error} Log level (default: info)
--version, -v Show version and exitโ๏ธ Configuration
Environment Variables
Configure the following environment variables:
# Required for trading operations
export HYPERLIQUID_PRIVATE_KEY="your_private_key_here"
# Optional: Specify a different user address for queries (defaults to wallet address)
export HYPERLIQUID_USER_ADDRESS="0x1234567890123456789012345678901234567890"
# Optional: Use testnet instead of mainnet (default: false)
export HYPERLIQUID_TESTNET="true"
# Optional: Show detailed logs for debugging (default: false)
export HYPERLIQUID_MCP_SHOW_LOGS="false"โ ๏ธ Security Warning: Never share your private key. The server will warn if the key is missing but will still start in read-only mode for market data.
Environment Variable Details
HYPERLIQUID_PRIVATE_KEY(Required for trading): Your wallet's private key for signing transactionsHYPERLIQUID_USER_ADDRESS(Optional): Ethereum address to query data for. If not set, uses the address derived from your private keyHYPERLIQUID_TESTNET(Optional): Set to"true"to use Hyperliquid's testnet for development and testingHYPERLIQUID_MCP_SHOW_LOGS(Optional): Set to"true"to enable detailed logging for debugging and development
๐ค User Address Configuration
The server supports querying data for different users:
Default behavior: Uses the address derived from your
HYPERLIQUID_PRIVATE_KEYCustom user: Set
HYPERLIQUID_USER_ADDRESSto query a different addressTool-level override: Many tools accept a
userparameter to query specific addresses
Use cases:
Monitor multiple accounts from one server instance
Query public data for other traders (positions, fills, etc.)
Portfolio management for multiple wallets
Analytics and research on other users' trading activity
๐งช Testnet Configuration
For development and testing, you can use Hyperliquid's testnet:
Enable testnet mode by setting
HYPERLIQUID_TESTNET=trueGet testnet tokens from the Hyperliquid testnet faucet
Use testnet-specific addresses - testnet has separate contracts and addresses
Test safely - All trades execute on testnet without real financial risk
๐ก Tip: Always test your trading strategies on testnet before using real funds on mainnet.
Claude Desktop Configuration
Add to your Claude Desktop claude_desktop_config.json:
{
"mcpServers": {
"hyperliquid": {
"command": "uvx",
"args": ["--no-progress","hyperliquid-mcp"],
"env": {
"HYPERLIQUID_PRIVATE_KEY": "your_private_key_here",
"HYPERLIQUID_USER_ADDRESS": "0x1234567890123456789012345678901234567890",
"HYPERLIQUID_TESTNET": "false",
"HYPERLIQUID_MCP_SHOW_LOGS": "false"
},
"transport": "stdio"
}
}
}Alternative Configurations
Using uv directly:
{
"mcpServers": {
"hyperliquid": {
"command": "uv",
"args": ["run", "--with", "hyperliquid-mcp", "hyperliquid-mcp"],
"env": {
"HYPERLIQUID_PRIVATE_KEY": "your_private_key_here",
"HYPERLIQUID_USER_ADDRESS": "0x1234567890123456789012345678901234567890",
"HYPERLIQUID_TESTNET": "false",
"HYPERLIQUID_MCP_SHOW_LOGS": "false"
},
"transport": "stdio"
}
}
}HTTP transport (for remote/multi-client setups):
โ ๏ธ Note: Environment variables (
HYPERLIQUID_PRIVATE_KEY, etc.) must be exported in the shell where the server is started โ they are not passed via the client config like with stdio.
# 1. Export env vars in your terminal
export HYPERLIQUID_PRIVATE_KEY="your_private_key_here"
export HYPERLIQUID_TESTNET="false"
# 2. Start the server
hyperliquid-mcp --transport http --port 3000Then configure your MCP client to connect:
{
"mcpServers": {
"hyperliquid": {
"url": "http://localhost:3000/mcp"
}
}
}Local development:
{
"mcpServers": {
"hyperliquid": {
"command": "uv",
"args": ["run", "hyperliquid-mcp"],
"cwd": "/path/to/hyperliquid-mcp",
"env": {
"HYPERLIQUID_PRIVATE_KEY": "your_private_key_here",
"HYPERLIQUID_USER_ADDRESS": "0x1234567890123456789012345678901234567890",
"HYPERLIQUID_TESTNET": "true",
"HYPERLIQUID_MCP_SHOW_LOGS": "true"
},
"transport": "stdio"
}
}
}๐ ๏ธ Available Tools
๐ค Account Management (5 tools)
get_positions
Get current trading positions and margin information.
Input:
user(optional) - Ethereum address to query (defaults toHYPERLIQUID_USER_ADDRESSor wallet address)Output: Positions and margin summary data
update_leverage
Modify leverage settings for a specific asset.
Input:
asset,leverage(1-100),is_isolated(boolean)Output: Leverage update confirmation
withdraw
Withdraw USDC to an external wallet.
Input:
destination(Ethereum address),amount(minimum $1.01)Output: Withdrawal confirmation
get_spot_user_state
Get spot trading account balances and state.
Input:
user(optional) - Ethereum address to queryOutput: Spot account balances and state
get_user_fees
Get user's current fee structure and rates.
Input:
user(optional) - Ethereum address to queryOutput: Fee information and tier details
๐ Market Data (5 tools)
get_market_data
Get current market data for a specific asset.
Input:
asset- Asset symbol (e.g., "BTC", "ETH")Output: Current price, volume, and market statistics
get_candle_data
Get historical OHLCV candlestick data.
Input:
asset,interval(1m, 5m, 1h, 1d, etc.),start_time,end_timeOutput: Historical price candles
get_l2_orderbook
Get Level 2 order book depth data.
Input:
asset,significant_figures(optional, 1-10)Output: Bid/ask levels with quantities
get_funding_rates
Retrieve current and historical funding rates for perpetual contracts.
Input:
asset(optional),include_history(boolean),start_time(optional)Output: Funding rate data
calculate_min_order_size
Calculate minimum order size for an asset to meet value requirements.
Input:
asset,min_value_usd(default: $10)Output: Minimum order size calculation
๐ Order Management (9 tools)
place_order
Place a new trading order on the exchange.
Input: Order details including:
asset- Asset symbolis_buy- Order direction (boolean)size- Order quantityorder_type- "market", "limit", or "trigger"price- Order price (required for limit/trigger)time_in_force- "GTC", "IOC", or "ALO"reduce_only- Reduce-only flag (boolean)take_profit- Take profit price (optional)stop_loss- Stop loss price (optional)
Output: Order placement confirmation with order ID
cancel_order
Cancel an existing order.
Input:
asset,order_idOutput: Cancellation confirmation
modify_order
Modify price, size, or time-in-force of an existing order.
Input:
asset,order_id,new_price(optional),new_size(optional),new_time_in_force(optional)Output: Modification confirmation
get_open_orders
Retrieve all currently open orders.
Input:
user(optional) - Ethereum address to queryOutput: List of open orders with details
get_order_status
Check the status of a specific order.
Input:
order_id,user(optional)Output: Order status and execution details
bulk_cancel_orders
Cancel multiple orders in a single request.
Input:
orders- List of orders with asset and order_idOutput: Bulk cancellation results
cancel_all_orders
Cancel all open orders, optionally filtered by asset.
Input:
asset(optional) - Filter by specific assetOutput: Mass cancellation confirmation
get_user_fills
Get recent trade executions (fills).
Input:
user(optional) - Ethereum address to queryOutput: Recent trade execution data
get_user_fills_by_time
Get user's trade fills within a specific time range.
Input:
start_time,end_time(optional),user(optional)Output: Trade execution history
๐งช Testing
The project includes comprehensive tests covering all tools:
# Run all tests
make test
# Run with coverage
make test-cov
# Run specific test categories (use direct command for specific targets)
uv run pytest tests/test_server.py::TestAccountTools -v๐ง Development
Setup Development Environment
# Clone the repository
git clone https://github.com/midodimori/hyperliquid-mcp.git
cd hyperliquid-mcp
# Install with development dependencies
make install-dev
# Run tests
make test
# Format and lint code
make format
# Check code style and types
make lint
# Run the server locally
make run
# See all available commands
make helpProject Structure
hyperliquid-mcp/
โโโ src/hyperliquid_mcp/
โ โโโ __init__.py
โ โโโ __main__.py # CLI entry point (argparse)
โ โโโ server.py # Server factory (create_server)
โ โโโ config.py # Pydantic configuration models
โ โโโ models.py # Request/response models
โ โโโ logging_config.py # Logging configuration
โ โโโ capabilities/ # MCP tool registrations
โ โ โโโ account.py # Account tools (5)
โ โ โโโ market.py # Market data tools (5)
โ โ โโโ order.py # Order management tools (9)
โ โโโ clients/ # Hyperliquid API clients
โ โ โโโ base_client.py # Base client & connection
โ โ โโโ account.py # Account operations
โ โ โโโ market.py # Market data operations
โ โ โโโ order.py # Order operations
โ โโโ transports/ # Transport runners
โ โโโ stdio.py # stdio transport (default)
โ โโโ http.py # Streamable HTTP transport
โ โโโ sse.py # SSE transport
โโโ tests/
โ โโโ test_server.py # Tool function tests
โ โโโ test_mcp_integration.py # MCP integration tests
โโโ pyproject.toml # Project configuration
โโโ README.md๐ API Reference
Order Types
market: Execute immediately at current market price
limit: Execute only at specified price or better
trigger: Stop/trigger order that becomes market order when triggered
Time in Force
GTC (Good Till Cancelled): Order remains active until filled or cancelled
IOC (Immediate or Cancel): Fill immediately or cancel unfilled portion
ALO (Add Liquidity Only): Only add liquidity, don't take from order book
Candle Intervals
Supported intervals: 1m, 3m, 5m, 15m, 30m, 1h, 2h, 4h, 8h, 12h, 1d, 3d, 1w, 1M
๐ค Contributing
Fork the repository
Create a feature branch (
git checkout -b feature/amazing-feature)Commit your changes (
git commit -m 'Add amazing feature')Push to the branch (
git push origin feature/amazing-feature)Open a Pull Request
๐ License
This project is licensed under the MIT License - see the LICENSE file for details.
โ ๏ธ Disclaimer
This software is provided for educational and informational purposes only. Trading cryptocurrencies involves substantial risk and may result in significant financial losses. The authors are not responsible for any trading losses incurred through the use of this software. Always conduct your own research and consider consulting with a qualified financial advisor before making trading decisions.
๐ Links
๐ Support
For questions, issues, or contributions:
Open an issue on GitHub
Check the Hyperliquid Discord for community support
Review the comprehensive test suite for usage examples
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/midodimori/hyperliquid-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server