AI Agents and Perp DEXs: What an MCP Server Actually Does

Guide · 6 min read · Verified 2026-07-30

⚠︎ Risk warning: leveraged derivatives on unregulated platforms — you can lose everything you deposit. Not investment advice.

A growing number of traders want to ask an AI assistant questions like "what's my worst position right now" or "which market has the most extreme funding" and get an answer from their actual account rather than a generic explanation. The plumbing that makes that possible is usually a Model Context Protocol server — MCP for short.

This guide covers what one actually is, which perp DEXs document official support, what those servers are permitted to do, and the one decision worth making carefully before you connect anything.

What an MCP server actually is

An AI assistant on its own can't reach the outside world. It can discuss Hyperliquid's funding mechanism from training data, but it can't see your position or today's rate. MCP is a standard way to hand it a set of specific, named capabilities — "fetch the order book", "list my open orders", "place this order" — that it can call when a question needs them.

The practical shape: an exchange publishes a server, you connect it to a client such as Claude Desktop, Claude Code or Cursor, and from then on the assistant can call those functions during a conversation. Each capability is a discrete tool, and the set of tools is what defines how much authority the assistant has. A server exposing only market-data tools can't touch your account no matter what you ask it.

Which venues document official support

Two of the venues we cover or compare have an MCP server you can use for trading today, a third documents one it has not shipped yet, and a fourth ships an official server that only reads its documentation — it cannot touch an account. For the rest we found nothing — which is a statement about what our search turned up, not proof that none exists. Checked against each venue's full documentation export rather than its page index (each row carries its check date); you can repeat it. Both caveats are load-bearing. Our first pass searched only the index and wrongly recorded GMX as having nothing, because GMX's MCP section sits inside a page body. And an export is not necessarily everything a venue publishes, so "none found" is where we stop rather than "none exists".

Worth noting what this isn't a ranking of. A venue without an MCP server isn't behind on API access — GMX documents an unshipped MCP server and publishes agent skills today, dYdX ships official SDKs in three languages, Lighter has one of the largest documented REST surfaces of any venue here, and Aster's API follows the Binance futures shape closely enough that general-purpose exchange clients work against it. MCP is a specific convenience for AI clients, not a proxy for developer support.

The two official servers do very different things

This is the part most coverage skips. Both Paradex and Pacifica document an official MCP server, but the authority they grant an assistant is not comparable.

Paradex documents 26 tools. Most are read-only — markets, order book, funding history, candles, your positions, fills and vault data. Two of them write: paradex_create_order places an order and paradex_cancel_orders cancels them. There is no tool that moves funds off the account.

Pacifica documents 58 tools, split 39 read and 19 write, and the write set is much broader: limit and market orders, stop orders, take-profit and stop-loss attachment, TWAP orders, batched actions of up to ten at once, leverage and margin-mode changes — and withdraw, which moves funds out of the perp account, plus withdrawSpotAsset, which its own documentation describes as queueing an on-chain withdrawal that is not reversible.

Neither is wrong. A trading agent that can't place orders isn't much of a trading agent, and Pacifica documents a read-only mode precisely because it knows the full set is a lot of authority. The point is that "has an official MCP server" is not one capability, and the right question isn't which venue has one — it's what you're handing it.

The permission decision

Before connecting any MCP server, exchange-published or not, settle one thing: what is the worst outcome if the assistant does something you didn't intend, or if the machine running it is compromised?

• Read-only is the safe default and covers most of what people actually want — portfolio questions, funding comparisons, "explain this position". Pacifica documents a read-only mode; Paradex notes you can skip the private-key step if you only need market data.
• Trading permission means an agent can open and close positions. Weigh that against the fact that a language model is not deterministic: it decides what to call in the moment, and the same prompt can produce different calls.
• Withdrawal permission is a different category entirely. An irreversible on-chain withdrawal is not a trade you can close. If a server exposes it and you don't need it, that is a strong reason to run in a restricted mode.

The same reasoning applies with more force to the unofficial servers on GitHub. Several exist for Hyperliquid and other venues, and some are well built — but they are third-party code you would be giving trading credentials to, they aren't audited by the exchange, and nothing obliges them to keep working after an API change. We don't recommend specific ones. If you evaluate one, read the source, and treat whatever key you hand it as the maximum you're prepared to lose.

Where to start

If you want to try this with the lowest stakes: connect a server in read-only mode and ask it things you can verify yourself, like the current funding rate on a market you're already watching. Our live funding table and execution-cost tool read the same public endpoints an MCP server would, so they're a decent cross-check on whether an agent is telling you the truth.

New to perps generally? Start with how perpetuals work and what a perp DEX is. For the venues themselves, our Hyperliquid vs Paradex and Hyperliquid vs Pacifica comparisons cover fees, custody and access.

Venue MCP status verified 2026-07-30 against each venue's own published documentation index. Tool names and counts are quoted from the two venues' own MCP tool references. This guide describes what the documentation permits; it is not a recommendation to grant an agent trading or withdrawal authority, and nothing here is investment advice.