hyperliquid-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PRIVATE_KEY | Yes | Your Hyperliquid wallet private key. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_spot_clearinghouse_stateB | Get the clearinghouse state of a user on Hyperliquid, if no user is provided, the clearinghouse state of the wallet address will be returned |
| get_perp_clearinghouse_stateB | Get the clearinghouse state of a user on Hyperliquid, if no user is provided, the clearinghouse state of the wallet address will be returned |
| get_order_statusB | Get the status of an order on Hyperliquid |
| get_open_ordersA | Get all open orders on Hyperliquid, if no user is provided, the open orders of the wallet address will be returned |
| get_order_historyA | Get all order history on Hyperliquid, if no user is provided, the order history of the wallet address will be returned |
| get_all_midsA | Get mid prices for all coins on Hyperliquid |
| get_spot_metaC | Request spot trading metadata |
| get_candle_snapshotB | Get candlestick data for a token on Hyperliquid |
| get_l2_bookB | Get the L2 book of a token on Hyperliquid |
| orderC | Place an order on Hyperliquid |
| cancel_orderC | Cancel an order on Hyperliquid |
| transfer_spot_perpA | Transfer spot to perp, or perp to spot, based on the toPerp value |
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 12 tools
The tools are mostly distinct, with clear separation between spot and perp clearinghouse states, and different order-related queries (status, open, history). There is slight potential confusion between 'order' and 'get_order_status', but descriptions clarify the intended purpose.
Most read-only tools follow the 'get_' prefix convention, but 'order', 'cancel_order', and 'transfer_spot_perp' do not, mixing bare verbs with the prefix pattern. The names are readable but not fully consistent in style.
With 12 tools, the server is well-scoped for its purpose, covering account state, order lifecycle, market data, and transfers without being overwhelming. Each tool serves a clear function within the trading domain.
The tool set covers core trading workflows, including querying state, managing orders, and fetching market data. Minor gaps exist, such as no explicit trade history, modify order capability, or position-specific endpoints, but these are workable for most use cases.