Hyperliquid MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HL_TESTNET | No | Set to 'true' to use the Hyperliquid testnet, or 'false' for mainnet. | |
| PAPER_TRADING | No | When 'true', orders are logged but never submitted to Hyperliquid. Set to 'false' to enable live trading. | true |
| HL_PRIVATE_KEY | No | The private key for the Hyperliquid wallet. Required for live trading. | |
| HL_WALLET_ADDRESS | Yes | The wallet address for the Hyperliquid account. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_account_infoA | Get wallet balance, margin summary, and withdrawable funds |
| list_marketsA | List all available perpetual futures markets on Hyperliquid |
| get_market_infoB | Get current price, funding rate, open interest, and 24h volume for a perpetual market |
| get_orderbookB | Get the orderbook (bids and asks) for a perpetual market |
| get_open_ordersB | List all open orders for the connected wallet |
| get_positionsA | List all open positions with unrealized PnL, leverage, and liquidation price |
| place_orderC | Place a limit or market order on Hyperliquid perps |
| cancel_orderB | Cancel an open order by order ID |
| set_leverageC | Set leverage for a perpetual market |
| close_positionB | Close an open position (market close or limit close) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool has a clearly distinct purpose in the trading lifecycle. Orders (place, cancel, get_open) are cleanly separated from positions (get, close), and market data tools (list_markets, get_market_info, get_orderbook) serve different information needs without overlap.
Excellent consistency throughout. All tools use snake_case with clear verb_noun or get_noun patterns (e.g., place_order, get_account_info, list_markets). The verb choices (place, cancel, close, get, list, set) are precise and predictable.
Ten tools is a reasonable scope for active trading operations, covering account, market data, orders, and positions. While the count is appropriate, a comprehensive trading surface might additionally include order history or modification tools, making it slightly lean.
Covers the core trading lifecycle well (account balance, market data, order management, position closing). Minor gaps include order history/fills, the ability to modify existing orders, and funding rate history—though agents can work around these by canceling/replacing orders and using current market data.