MCP connector · Live context

Connect Claude Code, Cursor, ChatGPT and other MCP clients

Hypertradeworx runs a Model Context Protocol server that gives an MCP client, such as Claude Code, Cursor or a ChatGPT connector, read access to your real portfolio: positions, balances, market data and more. With the trade scope it can also prepare a trade for you, and only you, to confirm in the app. No credential handed to a client can execute a trade by itself.

  • Live product data
  • Self-custodial
  • Human confirmed

What the connector does

The MCP server is served over streamable HTTP at POST https://mcp.hypertradeworx.xyz/mcp. Once connected, an MCP client can call a fixed set of tools to pull your live data on demand, the same data the app itself reads, rather than a snapshot you paste in manually. With the trade scope it can additionally stage a trade intent that you confirm in the app.

Two ways to authenticate

OAuth or an API key, whichever your client supports. With OAuth you add the server by URL and no key at all: the client discovers the authorization server, registers itself, and opens a browser page where you sign in to Hypertradeworx and approve the scopes it asked for, mcp:read and mcp:trade. This is the only path the ChatGPT and claude.ai web connectors accept, and it also works in Claude Code and Cursor. With an API key you mint a key in the app and pass it as a bearer header; nothing browser-interactive happens after setup.

Mint an API key

Create a key in the app at https://app.hypertradeworx.xyz/settings/connections and choose its scope: read only, or read + trade. The key starts with htw_ and is shown in full exactly once, at the moment it is created. Copy it immediately: the app cannot show it to you again, so if you lose it, mint a new one and update whichever client used the old value.

Connect Claude Code

With OAuth, add the server and sign in when the client prompts you. With an API key, pass it as a header instead. Run one of these once:

# OAuth: sign in via the browser when prompted (/mcp in Claude Code)
claude mcp add --transport http hypertradeworx https://mcp.hypertradeworx.xyz/mcp

# API key: mint the key first, then
claude mcp add --transport http hypertradeworx https://mcp.hypertradeworx.xyz/mcp \
  --header "Authorization: Bearer htw_<key>"

Connect Cursor or another MCP client

Any client that supports a streamable-HTTP MCP server can connect. Omit the headers block to use OAuth; keep it to authenticate with an API key. The shape below is the common convention; adjust it to wherever your client keeps its MCP server list.

{
  "mcpServers": {
    "hypertradeworx": {
      "url": "https://mcp.hypertradeworx.xyz/mcp",
      "headers": {
        "Authorization": "Bearer htw_<key>"
      }
    }
  }
}

Available tools

Nine tools are exposed. Eight are read-only and most of those are scoped to your own wallet; a few, like prediction market search, read public market data instead. The ninth, prepare_trade, is the only one that stages an action, and it requires the mcp:trade scope.

  • get_portfolio: open positions across every connected venue (Hyperliquid, Lighter, Ostium, GMX, AsterDex, Polymarket), with size, entry, mark, leverage and unrealised PnL. Positions only, not balances.
  • get_wallet_holdings: token balances. Scope to one chain or read every chain; low-value airdrop rows are flagged separately so they can be ignored.
  • get_perp_markets: perp market data, including per-venue aggregates and a given symbol across every venue that lists it, with max leverage. Rows older than 15 minutes are flagged as stale.
  • get_market_data: live Hyperliquid pricing only, mid prices or mark price, funding, open interest and 24h notional volume. Does not price positions on other venues.
  • get_predictions: Polymarket search, trending markets and event lookup, plus the in-house flash-predict feed. Not your own prediction positions, those come from get_portfolio.
  • get_lending_data: lending markets and your lending positions on Aave v3 and Compound v3.
  • get_watchlist: your saved watchlist entries.
  • get_alerts: your configured price alerts.
  • prepare_trade: stage a perp order (market, limit or close) on Hyperliquid, Ostium, GMX or AsterDex as a pending intent for you to confirm in the app. Requires mcp:trade.

How trading over MCP works

prepare_trade never places an order. It creates a trade intent and returns a confirmation link; the intent expires 2 minutes after creation and can be confirmed at most once. Opening the link in the web app while signed in is the only way to execute it: the confirm step rejects every API key and OAuth token, including the credential that created the intent, so no client, script or agent can complete a trade on its own. Close orders are supported on Hyperliquid only, and Lighter, Polymarket and swaps are not reachable through this tool. A read-only credential calling prepare_trade gets a permission error, not a silent drop.

Straight answers

Frequently asked questions

Can an MCP client place trades on its own?
No. With the mcp:trade scope it can prepare an order, which creates an intent that expires in 2 minutes. Executing it requires you to open the confirmation link in the web app while signed in. The confirm step rejects every API key and OAuth token, including the one that created the intent.
Where do I create a key?
In the app, at https://app.hypertradeworx.xyz/settings/connections. Pick read only or read + trade when you mint it. The key is shown in full once, at creation.
What if I lose the key after closing the page?
It cannot be shown again. Mint a new one from the same settings page and update the client that was using the old value.
Can I connect this to ChatGPT or claude.ai as a web connector?
Yes. Add https://mcp.hypertradeworx.xyz/mcp as the connector URL. Both flows use OAuth: you are sent to the Hypertradeworx app to sign in and approve access, and no API key is involved.
Why does prepare_trade fail with a permission error?
Your credential only carries mcp:read. Mint a new key with read + trade, or reconnect via OAuth and approve the trade scope on the consent screen.
Connected to your account

Take the next step in Hypertradeworx

Move from reference to the live product when you are ready.