Two years ago, wiring an AI model into a live market meant gluing together brittle scripts and hoping the exchange didn't change an endpoint on you. That era is over. By mid-2026 nearly every venue a retail trader cares about — a US brokerage, an onchain DeFi network, a perpetuals DEX, a regulated prediction market — either ships an official Model Context Protocol server or has a community one that works. This is the directory we wish we'd had: the trading MCP servers worth your time in 2026, grouped by what they connect to and, more importantly, by who holds your money when the agent makes a mistake. Each one links to our full setup guide.
How Should You Choose an MCP Server for Trading?
Start with custody, not features. The question that should decide your first server isn't "how many tools does it expose?" — it's "when my agent does something dumb, what's the worst it can do?" A slick 40-tool toolkit on a self-custody wallet has a larger blast radius than a plain read-and-trade server on a brokerage account, because the first can sign a transfer to an attacker and the second cannot. Custody model is the axis that actually protects your balance.
Four things separate a server you should trust from one you shouldn't, and none of them is polish:
- Custody model. Brokerage OAuth (funds stay at a regulated broker), agent-wallet (an agent can trade but not withdraw), or self-custody (the agent holds a private key that controls the coins). This is the single most important line in the table below.
- Jurisdiction. US traders can't lawfully touch the international Polymarket book; non-US traders can't open a Robinhood account. Availability isn't a footnote — it decides which servers are even an option for you.
- Read-only support. A good server lets the agent see the market with just a public address or a scoped read key, before you ever hand it signing power. If a server demands a trading key to do anything at all, that's a mark against it.
- Safety surface. Does the venue itself give you a kill switch — a revocable agent key, an OAuth token you can pull, a segregated account? The more of the safety story the venue carries, the less rides on your own discipline.
Hold those four in mind as you read. Here's the whole field on one screen.
The Trading MCP Servers Worth Covering in 2026
Below is every server we've written a setup guide for, grouped by type. Custody is the column to read first; jurisdiction is the one that decides whether a row applies to you at all.
| Server / venue | Connects to | Custody model | Availability | Our setup guide |
|---|---|---|---|---|
| Robinhood Trading MCP | US brokerage: stocks & options | Brokerage OAuth (funds at broker) | US | Robinhood guide |
| Robinhood Agentic Crypto | Brokerage crypto, 24/7 | Brokerage OAuth (funds at broker) | US (eligible customers) | Agentic crypto guide |
| Hyperliquid MCPs | Onchain perpetuals DEX | Agent (API) wallet — trades, can't withdraw | International | Hyperliquid guide |
| Coinbase Base MCP | Onchain DeFi on Base | Self-custody (you hold the keys; per-action approval) | Global (US access varies) | Coinbase Base guide |
| Kalshi | US-regulated prediction market | API key; USD held at a CFTC-regulated DCM | US (40-plus states) | Kalshi guide |
| Polymarket | Prediction market (onchain, Polygon) | Self-custody wallet (intl); regulated US market | International (+ regulated US) | Polymarket guide |
| CCXT-style multi-exchange | 100-plus centralized crypto exchanges | Exchange API keys (funds at each exchange) | Varies by exchange | Community servers (no first-party guide yet) |
Brokerage OAuth: Robinhood Trading and Agentic Crypto
Robinhood was the first major US consumer brokerage to ship an official MCP server, and for a lot of traders it's the sanest place to start. The custody story is the reason: your money stays inside a regulated brokerage account, and the agent reaches it through an OAuth grant you can revoke from Robinhood's own app. There's no private key sitting in a config file, no wallet for the agent to drain. Pull the token and the agent is instantly, completely locked out.
The Trading MCP covers US stocks and options through a single configuration URL, and it's model-agnostic — the same endpoint works whether you drive it with Claude, ChatGPT, or something else. The agentic crypto variant points the identical mechanism at a market that never closes, which is exactly where an always-on hosted agent starts to matter and a laptop-bound one starts to fail. The honest limitation is jurisdiction: this is US-only, and non-US traders will have to look elsewhere on this list.
Agent Wallets: The Hyperliquid MCP Servers
Hyperliquid is where crypto's most active perpetuals traders live, and its agent wallet is quietly one of the best safety features on this whole list. When you approve an agent wallet, you're handing over a permissioned signer that can place and manage trades on your account but — per Hyperliquid's own docs — does not hold your funds and can't withdraw them. The worst a compromised agent key can do is trade badly. It can't sign a withdrawal to a stranger's address. That's a structurally smaller blast radius than self-custody, and it's why we point newcomers to onchain agent trading here first.
You have three realistic ways to wire it, and they trade convenience for control. Senpi's toolkit is the most complete agent-native interface, with an open-source skill library worth reading even if you roll your own. HyperLiquid-Claw is a Rust-based skill that runs read-only with just your public address and asks for a signing key only when you actually want it to place orders. And edkdev/hyperliquid-mcp is the option for people who'd rather run the plumbing themselves and keep every dependency in view. Our Hyperliquid guide walks all three. The catch that no wallet design fixes: perps use leverage, so size for the liquidation, not for comfort.
Self-Custody: The Coinbase Base MCP
Coinbase's Base MCP is the most capable server here and, not coincidentally, the one that demands the most discipline. It lets an agent hold a wallet on Coinbase's Base network and act across DeFi — swap tokens, supply to lending vaults, settle onchain payments — on a market that runs around the clock. If you want an agent that doesn't just trade but actually operates onchain, this is the deepest surface on the list.
It's also the row where custody is fully yours. Base MCP is non-custodial — no broker, no permissioned agent wallet between you and the coins — and Coinbase's own server hands the agent no raw private key, drafting each write action for you to approve within spend caps it can't change. But self-custody still puts the safety story on you: a misfired or prompt-injected agent, a rushed approval, or a broad token allowance can move funds with no recourse and no support desk to call. So the setup discipline is non-negotiable — a dedicated low-balance hot wallet, the bulk of your holdings in cold storage the agent can't reach, and per-trade caps plus a token whitelist in a persistent skill. Power and blast radius are the same coin here. Fund it accordingly.
Prediction Markets: Kalshi and Polymarket
Prediction markets are a natural fit for an always-on agent, because they reprice the instant news breaks and often resolve overnight while you sleep. Your choice between the two big ones is mostly decided for you by where you live. Kalshi is a CFTC-regulated Designated Contract Market, legal across 40-plus US states, funded in US dollars with no crypto and no VPN games. You authenticate with an RSA key pair and can rehearse against a real demo sandbox before a cent is at risk — one of the cleaner safety surfaces on this list.
Polymarket is the mirror image: the largest prediction market in the world, but the main book is an international onchain exchange on Polygon that US residents can't lawfully use. US traders are limited to the newer CFTC-regulated Polymarket US with full KYC and USD settlement; everyone else funds a self-custody Polygon wallet with USDC and generates CLOB API credentials. Same category, opposite custody and jurisdiction — which is exactly why the two share a section but not a setup.
What About General and Community Servers?
Beyond the venue-specific servers, a whole tier of community and general-purpose MCPs exists — most visibly the CCXT-style multi-exchange servers that wrap the long-running CCXT library to reach 100-plus centralized crypto exchanges through one interface. The appeal is obvious: one server, many venues, funds sitting at each exchange under that exchange's own API-key permissions. If your strategy spans several centralized exchanges, this is the pragmatic route.
The trade-off is just as real. Community servers don't carry the vendor accountability of a first-party release like Robinhood's or Coinbase's, and quality varies from project to project. Before you wire one to a funded account, read the code, scope every exchange API key to trading-only with withdrawals disabled, and treat it as read-only until it's earned more. We don't have a dedicated setup guide for these yet, so the burden of vetting sits with you — which is the right posture for any community server holding trading keys.
How Do You Actually Run One of These Safely?
The server is only half the setup. The other half is where the agent runs and what rails constrain it — and that half is identical no matter which row of the table you pick. A study of 925,323 wallets on AI-agent trading platforms, run by researchers at Stanford, Pantera, and IC3, found users lost close to $192 million, with 62.2% ending up down. Handing a smarter model the keys doesn't put you in the winning minority. Disciplined limits do, and those limits have to live somewhere they can't be forgotten.
That "somewhere" is a persistent safety skill, not a chat message — because context compaction silently erases chat instructions, and a rail that vanishes mid-session was never a rail. Our safety hub lays out the seven that every one of these venues needs: a segregated account with a funding cap, per-trade and daily caps, an instrument whitelist, a leverage ceiling, a liquidity floor, a human in the loop, and two independent kill switches with an audit trail you actually read. Wire that skill once and attach it to every server on this list.
And run it somewhere that stays online. Every venue here reprices while you sleep, so an agent on a laptop that dozes off is an agent that misses the move that mattered. That's the whole reason we host these on dedicated Instances — the same shape of stack, whichever server you choose.
One home for any trading MCP on this list
OpenClaw Direct runs your agent on an isolated Instance with an encrypted vault, 99.9% uptime, and a full audit trail — model-agnostic, controllable from Telegram. Advanced is $29/mo, and free trial credits come with every subscription.
Run OpenClaw NowWhere to Start
If you're new to this, the boring answer is the right one: pick the row with the smallest blast radius that matches where you live. For US traders that's usually Robinhood or Kalshi, where funds stay at a regulated venue and a revoked token or key ends the agent's access cleanly. For onchain traders, Hyperliquid's agent wallet is the gentler on-ramp; save the full self-custody power of Coinbase Base for after you've watched an agent behave for a few weeks.
Whichever you choose, the pattern is the same across every guide on this list. Understand the custody model, attach the safety rails before the agent can trade, start read-only, add Telegram approvals, and size your first live stake down to something you'd be annoyed — not wrecked — to lose. The MCP is just the connector. The discipline is what keeps you solvent.
Sources: Base — Introducing Base MCP, Hyperliquid Docs — Nonces and API Wallets, HyperLiquid-Claw — MCP trading skill for OpenClaw, GitHub — edkdev/hyperliquid-mcp, GitHub — CCXT crypto exchange library, GitHub — Polymarket Agents framework, and Yu, Zhao & Sui (Stanford / Pantera / IC3) — Paper Agents, Paper Gains: An Empirical Analysis of DeFi Investment Agents.