Hyperliquid MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HYPERLIQUID_TESTNET | No | Set to "true" for testnet, "false" or unset for mainnet | |
| HYPERLIQUID_PRIVATE_KEY | No | Your wallet's private key (with 0x prefix) - required for trading operations | |
| HYPERLIQUID_WALLET_ADDRESS | No | Your wallet address (derived from private key if not provided) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_all_midsB | Get current mid prices for all coins on Hyperliquid |
| get_l2_bookC | Get L2 order book snapshot for a specific coin |
| get_candle_snapshotC | Get historical candle data for a specific coin |
| get_open_ordersB | Get all open orders for the configured wallet or a specific user |
| get_user_fillsB | Get trading history (fills) for the configured wallet or a specific user |
| get_user_fills_by_timeB | Get trading history (fills) for a specific time range |
| get_portfolioC | Get portfolio information including positions, PnL, and margin usage |
| place_orderC | Place a limit or trigger order on Hyperliquid |
| place_trigger_orderC | Place a trigger order (stop-loss or take-profit) on Hyperliquid |
| cancel_orderB | Cancel a specific order by order ID or client order ID |
| cancel_all_ordersB | Cancel all open orders |
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 11 tools
Each tool has a clearly distinct purpose with no significant overlap. For example, cancel_all_orders vs cancel_order handle different cancellation scopes, and get_user_fills vs get_user_fills_by_time provide historical data with different filtering approaches. The descriptions make it easy to distinguish between trading actions, data queries, and order management functions.
All tools follow a consistent verb_noun naming pattern with snake_case throughout. The verbs are clear and appropriate (get, cancel, place) and the nouns specify the exact resource or action. There are no deviations in style or convention across the 11 tools.
With 11 tools, this server provides comprehensive coverage for cryptocurrency trading on Hyperliquid without being overwhelming. The count aligns well with the domain scope, covering order placement/cancellation, market data access, portfolio tracking, and trade history—all essential functions for trading automation.
The toolset covers most core trading operations including order management, market data, portfolio tracking, and historical fills. A minor gap exists in account management tools (e.g., deposit/withdrawal, funding rates) and advanced order types beyond limit/trigger orders, but agents can execute basic to intermediate trading workflows effectively.