claude mcp add robinhood-trading: the exact command, and the flag that makes it work
One line does the connection. The bare form of it registers the wrong kind of server, which is the most common reason it “can’t connect.”
Coil is not affiliated with Robinhood or Anthropic. This page documents a third party’s public endpoint as it stood on 2026-09-01, checked against the live server; if their address changes, theirs is right and this page is wrong.
1. The command
claude mcp add --transport http robinhood-trading https://agent.robinhood.com/mcp/tradingConfirm that address on Robinhood’s own agentic-trading page before you paste it. The endpoint is theirs — Coil doesn’t run it, doesn’t proxy it, and never sees anything that crosses it. No credential goes in that line.
2. Why the flag matters
A bare claude mcp add NAME ARG tells Claude Code to launch the argument as a local program and talk to it over stdio. A URL is not a program, so the registration succeeds and the server never answers. --transport http is what tells it the server is remote. This single omission is the largest share of “Claude can’t connect to Robinhood” we see, and it produces no error at add time.
3. What happens next
On first use, your browser opens a robinhood.com login page. You sign in and approve the connection there. That is the whole security property of the design: Claude never holds your password, and you can revoke the connection from inside Robinhood without touching Claude at all.
4. Prove it with a read before you trust it with an order
Ask Claude for your account summary or your positions. A successful read means the connection is live. If reads work and orders are refused, the command is fine and the cause is the account — agentic trading has to be switched on inside the Robinhood app, and the server rejects orders from any account without it. The five reasons a connected agent still won’t trade are each diagnosed at the troubleshooting guide.
5. The other half of the setup
The Robinhood server gives your agent hands. What to buy, when to enter, and when to stand aside is a separate problem, and it is the one Coil sells: a scored board and a served rulebook delivered over a second MCP line in exactly the same shape — claude mcp add --transport http coil https://coil.trade/mcp. The free tier is a delayed board with no key; Coil Live ($29/mo) serves the live board with structural stops and the discipline the record trades by; the Coil Engine ($79 once) runs those rules on your own machine. That record is published at /results whether it is up or down.
Common questions
Why does claude mcp add robinhood-trading followed by the URL register the wrong kind of server?
Because a bare claude mcp add NAME ARG registers a local command — Claude Code assumes the argument is a program to launch over stdio. Robinhood's endpoint is a remote HTTP server, so it needs the transport named explicitly: --transport http. Without the flag the add succeeds, the server never answers, and the failure reads as 'can't connect'.
Does the command need my Robinhood password?
No, and it must not. The command only registers the address. Authentication happens at the next step, in your own browser on robinhood.com through OAuth, where you sign in and approve the connection. Nothing you type into Claude Code carries a credential.
Is agent.robinhood.com Coil's server?
No. It is Robinhood's own endpoint for their agentic-trading program; Coil does not run it, proxy it, or see anything that crosses it. Confirm the address on Robinhood's agentic-trading page before you paste it — they can change it, and a stale URL copied from any third-party guide is how a broker connection gets phished. Coil's own MCP server is a separate line: claude mcp add --transport http coil https://coil.trade/mcp.
It connected, but Claude won't place a trade. Now what?
That is a different problem with five distinct causes — the agentic account not enabled, the confirmation step, a symbol restriction, buying power, or the order type. Each is diagnosed in its own words at coil.trade/guides/robinhood-mcp-troubleshooting.