Hyperliquid MCP Server v2

Created By
TradingBalthazara year ago
A Model Context Protocol server for Hyperliquid with integrated dashboard
Overview

What is Hyperliquid MCP Server v2?

Hyperliquid MCP Server v2 is a Model Context Protocol server designed for interacting with the Hyperliquid exchange API, featuring an integrated dashboard for account management.

How to use Hyperliquid MCP Server v2?

To set up the server and dashboard, clone the repository and run the setup command. Access the dashboard at http://localhost:3000 after setup.

Key features of Hyperliquid MCP Server v2?

  • One-command setup for quick initialization
  • Authentication via private keys or wallet addresses
  • Trading capabilities including placing and canceling orders
  • Real-time market data retrieval
  • Custom trading strategy management
  • User-friendly dashboard for account monitoring

Use cases of Hyperliquid MCP Server v2?

  1. Automating trading strategies on the Hyperliquid exchange.
  2. Monitoring account performance and market data in real-time.
  3. Managing perpetual and spot trading positions effectively.

FAQ from Hyperliquid MCP Server v2?

  • Can I use the server for both testnet and mainnet trading?

Yes! You can toggle between testnet and mainnet for safe testing.

  • Is there a way to create custom trading strategies?

Yes! You can create and customize strategies using HL Coder.

  • How secure is my data with the MCP server?

The server stores credentials in memory only and uses secure input fields for sensitive information.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
TradingBalthazar
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago