HL Portfolio API MCP Server

Hyperliquid account analysis: positions, PnL, fills, orders, funding. x402 pay-per-call.

Local serverstdio

What is the HL Portfolio API MCP server?

HL Portfolio API MCP server exists for a simple reason — assistants are far more useful when they can act on HL Portfolio API directly instead of describing what you should do. Hyperliquid account analysis: positions, PnL, fills, orders, funding. x402 pay-per-call.

What you get

Analyze Hyperliquid accounts: positions, PnL, fills, open orders, funding. Full clearinghouse state for any wallet. The portfolio layer agents need for Hyperliquid trading intelligence. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.

What the assistant can call

Once HL Portfolio API is connected, these are the calls the assistant has available:

  • hyperliquid_get_account_state — POST
  • hyperliquid_get_trade_fills — POST
  • hyperliquid_get_open_orders — POST
  • hyperliquid_get_user_funding — POST

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. HL Portfolio API's toolset — hyperliquid_get_account_state, hyperliquid_get_trade_fills, hyperliquid_get_open_orders and 1 more — is a fair guide to whether it matches your workflow. It is maintained by Br0ski777; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the hl portfolio api mcp server does with a few real requests.

Available tools

ToolWhat it does
hyperliquid_get_account_statePOST
hyperliquid_get_trade_fillsPOST
hyperliquid_get_open_ordersPOST
hyperliquid_get_user_fundingPOST

How to install the HL Portfolio API MCP server

{
  "mcpServers": {
    "hl-portfolio": {
      "url": "https://hl-portfolio.api.klymax402.com/mcp"
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Example prompts to try

  • Use HL Portfolio API to hyperliquid get account state.
  • Use HL Portfolio API to hyperliquid get trade fills.
  • Use HL Portfolio API to hyperliquid get open orders.

Frequently asked questions

It connects HL Portfolio API to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (hyperliquid_get_account_state, hyperliquid_get_trade_fills, hyperliquid_get_open_orders, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with HL Portfolio API directly.