Connect your AI
MCPify runs a hosted Hyperliquid MCP server — the shortest path to AI crypto trading over the Model Context Protocol, the open standard AI clients use to reach real tools. Point Claude at your personal connector URL and it can read live Hyperliquid markets, inspect your account, and — once you arm it — place and manage orders through the same trade-only key the terminal uses. Withdrawals are impossible through MCP by construction.
A USB port for AI assistants
The Model Context Protocol is an open standard that lets an AI client talk to an external service through a small, typed set of tools. Instead of pasting screenshots into a chat, your assistant calls get_my_account or place_order directly and gets structured data back. MCPify runs a dedicated MCP server so any compliant client — Claude web and desktop, Claude Code, Cursor, or your own agent — can trade your Hyperliquid account without a scraper, a screenshot, or your private key.
Your own private endpoint
Each account gets a URL with a personal key inside it. Nothing is shared between users, and one click revokes it.
Typed tools, not prompts
The AI does not "guess" a UI. It calls documented tools with validated parameters and receives structured JSON.
The same rails as the terminal
Agent orders go through the identical execution path, caps and audit log as orders you place by hand.
Three steps to an agent that trades
01Generate your connector key
The key is shown once and stored only as a hash. It carries read access immediately; order placement stays off until step two.
https://mcp.mcpify.trade/mcp?token=mcpf_••••••••••••••••Connect your wallet to generate a personal connector URL.
02Arm agent trading
Off by default. When armed, your AI can place orders through the same trade-only key you approved for the terminal — under hard server caps it can never exceed. Flip it back off at any moment; the change is instant.
03Add the connector to your client
Pick your client below. The URL is the same everywhere — only where you paste it changes.
Open claude.ai → Settings → Connectors → Add custom connector
Paste your connector URL and leave authentication on “None” — the key travels inside the URL
Save, then start a new chat: the MCPify tools appear in the tools menu
What a session looks like
Once connected, you trade in plain language. The assistant calls the tools, restates what it is about to do, and reports the fill — and every one of those calls lands in your history.
Twelve tools, four of them armed
Read tools — always available
get_marketsEvery tradable perp with price, 24h change, volume, funding and max leverage.
get_priceLive mark price and 24h stats for one market.
get_orderbookLive bids and asks with configurable depth.
get_candlesOHLCV history for any supported interval, for analysis or charting.
get_my_accountBalance, withdrawable, open positions with PnL and liquidation prices.
get_my_open_ordersResting and trigger orders, each with the id needed to cancel it.
get_my_trade_historyRecent fills from Hyperliquid: price, size, fee, realized PnL.
get_my_order_recordsYour MCPify audit records — including which source placed each order.
Trading tools — only when armed
place_orderOpen a position: market or limit, cross or isolated, optional TP/SL attached on fill.
close_positionClose fully or partially at market. Risk-reducing, so it stays available while armed.
set_position_tp_slSet or replace take-profit and stop-loss triggers on an open position.
cancel_orderCancel a resting or trigger order by id.
Deliberately missing
There is no withdraw tool, no transfer tool, and no way to change your account settings from MCP. Even if a tool existed, the agent key it would sign with is restricted by Hyperliquid to trading actions.
Guardrails you cannot prompt your way past
Per-order and per-day caps
Margin per order, leverage, orders per minute and orders per day are enforced on our servers, not in the prompt. The assistant is told about them and refused when it exceeds them.
Instant revocation
Revoking the connector key or disarming trading takes effect on the very next tool call — no session to expire, no cache to wait out.
Duplicate and race protection
Identical orders inside a 15-second window are suppressed, and actions on the same market are serialized so a stop can never be cancelled without its replacement landing.
A full paper trail
Every tool call is logged with its parameters, outcome and the client that made it. Your Portfolio page shows which orders came from an agent.
MCP, answered
What is the Model Context Protocol?
MCP is an open standard for connecting AI assistants to external tools and data. A service exposes a small set of typed tools; a client like Claude discovers them and calls them on your behalf. It replaces brittle screen-scraping with a real, documented interface.
Is there an MCP server for Hyperliquid?
Yes — MCPify runs a hosted Hyperliquid MCP server, with nothing to install or self-host. Sign in with your wallet, generate your personal connector URL on this page and paste it into your client: you get live market data, your account state and — once you arm it — real order execution over the Model Context Protocol.
Which clients work with this connector?
Anything that speaks MCP over streamable HTTP: Claude on web, desktop and mobile, Claude Code, Cursor, Goose, VS Code extensions, and custom agents built on the MCP SDKs. The endpoint is a single URL and the key can travel in the URL or in an Authorization header.
Can Claude actually trade crypto with real money?
Yes. Through this connector Claude places real perpetual-futures orders on Hyperliquid, with real USDC margin, on your own account — the same is true for Claude Code, Cursor or any MCP client. You stay in control three ways: order placement is off until you arm it, hard server-side caps bound margin, leverage and order rate, and the key the AI uses can never withdraw.
Can the AI withdraw my money?
No, in two independent ways. First, no withdraw or transfer tool exists on the server, so there is nothing to call. Second, the key those tools would sign with is a Hyperliquid agent key, which the protocol itself forbids from withdrawing. Withdrawals require a signature from your own wallet, which lives in your browser extension.
What stops the AI from over-trading or making a huge mistake?
Server-side caps: a maximum margin per order, a maximum leverage, and limits on orders per minute and per day. They are enforced after the request reaches us, so no prompt can talk the server out of them. Identical orders inside fifteen seconds are also suppressed, and actions on the same market are serialized.
Is agent trading on by default?
No. A fresh connector key is read-only. You have to flip “Agent trading” on yourself, and you can flip it back off at any time — the next tool call is already blocked.
What happens if my key leaks?
Revoke it on this page. Revocation is immediate and also disarms agent trading, so a new key has to be armed again explicitly. A leaked key never grants withdrawals, and it can be regenerated as often as you like.
Does the AI see my private key or seed phrase?
Never. Your private key stays in your wallet extension and is never transmitted anywhere. The connector reaches only the restricted agent key held by our execution service.
Are there usage limits on the tools themselves?
Yes — a generous daily quota on tool calls per account, plus the trading caps above. The current values for your account are shown in the “Agent trading” panel on this page.
Can I see what the AI did afterwards?
Yes. Every tool call is logged, and every order records the source that placed it. Your Portfolio page marks agent-placed orders so you can review a session after the fact.