Hyperliquid MCP Server

What is Hyperliquid MCP Server?

A Model Context Protocol (MCP) server that enables interaction with the Hyperliquid exchange API through HL Coder or Claude, supporting trading, market data, and strategy management.

How to use Hyperliquid MCP Server?

Install by cloning the repository, running npm install and npm run build, then configure the server in your HL Coder settings file using the path to build/index.js. An optional companion dashboard (Next.js) is available for credential management and balance viewing. Use the server’s tools to authenticate, fetch market data, place orders, and create trading strategies.

Key features of Hyperliquid MCP Server

• Authenticate with private keys or wallet addresses
• Place and cancel orders on Hyperliquid
• Retrieve real-time market data for trading pairs
• Create and manage custom trading strategies
• Credentials stored in memory only
• Full testnet support for safe development

Use cases of Hyperliquid MCP Server

• Automate trading strategies on Hyperliquid via AI assistants
• Monitor real-time market data for BTC-PERP and other pairs
• Test order placement and strategy logic on testnet before going live
• Manage multiple Hyperliquid accounts from a centralized interface

FAQ from Hyperliquid MCP Server

What tools does the server provide?

The server provides tools to authenticate, get market data, place orders, and create strategies. Specific tool names include authenticate, get_market_data, place_order, and create_strategy.

How do I install the Hyperliquid MCP Server?

Clone the repository, run npm install then npm run build, and add a configuration block in your HL Coder settings file pointing to the built index.js.

What are the security considerations?

Credentials are stored only in memory. Always use testnet ("testnet": true) for testing before using real funds on mainnet. Never share private keys or expose them in public repositories.

Is a dashboard required to use the server?

No, the dashboard is optional. It is a separate Next.js project for managing credentials and viewing account balances, but the core server works independently.

Does the server support both mainnet and testnet?

Yes, the authenticate tool accepts a testnet parameter to switch between testnet and mainnet environments.