Model Context Protocol

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. Add one URL to Claude, ChatGPT or Claude Code, sign in with your wallet, and your assistant 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.

Setup timeUnder a minute
Order toolsOff until you arm them
Withdraw toolsNone, ever
Agent session · Claude
What is MCP?

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, ChatGPT, Cursor, or your own agent — can trade your Hyperliquid account without a scraper, a screenshot, or your private key.

Sign in, don’t paste secrets

Claude and ChatGPT connect through an MCPify sign-in that shows which app is asking and lets you decide whether it may trade. Every app can be disconnected in one click.

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.

Setup

Connect in under a minute

01Add the server URL

One URL for every client. Claude, ChatGPT and Claude Code open an MCPify sign-in the first time: you connect your wallet, see exactly which app is asking, choose whether it may trade, and click Allow. Nothing to copy, nothing secret in the URL.

MCP server URL
https://mcp.mcpify.trade/mcp

A client that cannot open a sign-in window (Cursor, n8n, a script, Claude Code on a server) uses a personal key instead — see “Cursor & others” below.

02Connect your client

Pick your client. The URL is the same everywhere — only where you paste it changes.

01

Open claude.ai → Settings → Connectors → Add custom connector. Name it MCPify, paste the server URL and click Add — leave the advanced OAuth fields empty

claude · connectors
NameMCPify
https://mcp.mcpify.trade/mcp
CancelAdd
02

Click Connect. Claude opens the MCPify sign-in: connect your wallet, review the request, keep or untick Allow trading, then click Allow access

mcpify.trade · connect
Allow Claude to use your MCPify account?
claude.ai
✓Allow trading
DenyAllow access
03

Start a new chat: the MCPify tools are in the tools menu. Claude Desktop and the mobile apps pick the connector up from your account

claude
MMCPify Connected
how is my account?
$4,182 · 1 position ✓

Connected before with a ?token= URL? It keeps working. To switch, remove that connector and add the plain URL — your personal key stays valid for other clients until you revoke it.

03Arm 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. This switch covers every connection; each app also has its own trading permission below. Flip it off at any moment; the change is instant.

Max margin / order
$1000
Max leverage
40×
Orders / day
1000
Calls / day
∞
Disarmed — read-only

Connected apps

Connect your wallet to arm trading and manage your connected apps.

In practice

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.

Agent session · Claude
Capabilities

Fourteen tools, four of them armed

Read tools — always available

get_markets

Every tradable perp with price, 24h change, volume, funding and max leverage.

get_price

Live mark price and 24h stats for one market.

get_orderbook

Live bids and asks with configurable depth.

get_candles

OHLCV history for any supported interval, for analysis or charting.

get_my_account

Balance, withdrawable, open positions with PnL and liquidation prices.

get_my_positions

Each open position with entry, mark, liquidation, PnL — and the TP/SL orders protecting it.

get_my_open_orders

Resting and trigger orders, each with the id needed to cancel it.

get_my_trade_history

Recent fills from Hyperliquid: price, size, fee, realized PnL.

get_my_order_records

Your MCPify audit records — including which source placed each order.

preview_order

Sizes and checks an order without placing it — the proposal the user confirms.

Trading tools — only when armed

place_order

Open a position: market or limit, cross or isolated, optional TP/SL attached on fill.

close_position

Close fully or partially at market. Risk-reducing, so it stays available while armed.

set_position_tp_sl

Set or move take-profit and stop-loss on an open position — a leg you leave out stays as it is.

cancel_order

Cancel 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.

Safety

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

Disconnecting an app, revoking a 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.

Questions

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 at https://mcp.mcpify.trade/mcp, with nothing to install or self-host. Add that URL to your client and sign in with your wallet: 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 (web, desktop and mobile), Claude Code, ChatGPT, Grok and Perplexity connect with the plain URL and an MCPify sign-in. Cursor, Windsurf, VS Code, n8n and custom agents can use a personal key instead, in the URL or as an Authorization header.

How does signing in from Claude or ChatGPT work?

It is standard OAuth. Your AI app sends you to mcpify.trade, you connect your wallet, and a consent screen shows which app is asking, where the access goes and whether it may trade. The app receives a token that only works on the MCPify connector — it cannot sign in to the MCPify website, it expires within the hour and renews only while you keep the app connected, and it can never withdraw.

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 ChatGPT, 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. Every new connection only reads until you flip “Agent trading” on yourself — and each app you sign in also has its own “Allow trading” permission, chosen on the sign-in screen and changeable on this page. Flip either off and the next tool call is already blocked.

What if I stop trusting an app, or my key leaks?

Disconnect the app on this page, or revoke the personal key — either takes effect on the very next call, and “Disconnect all apps” ends every sign-in at once. Neither an app nor a key ever grants withdrawals, and a key 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.