What people are actually getting to work with the Robinhood MCP

Get the agent to actually execute — the wall most people hit

The most common failure isn't a bad strategy, it's that the agent researches and recommends but won't pull the trigger, or is stuck read-only. The people who break through:

• Drive it from Claude Code / Codex / Cowork, never bare chat — bare chat is where refusals and read-only behavior live. Robinhood gives the MCP; your agent runtime is the agent.
• Turn developer mode on to add the connector:

• When it still refuses: paste the Robinhood MCP docs URL into the chat — people report it flips to "oh, my bad" and starts executing.
• Or run Sonnet with thinking off, drop phrases like capital allocation / % per trade, state you're the final decision-maker who accepts the losses, and stay in the one chat that works — a fresh chat re-triggers the refusal.
• In Codex, auto-approve MCP calls in config. Robinhood still forces a per-trade human approval; one user routes that approval to email with a Gmail auto-reply. Removes a real safety gate — the cleaner version keeps approval and makes only the proposal deterministic.

Reality check: truly hands-off needs a wrapper (cron + a rules file), and Claude Code has to stay open — it trades while your machine is on, not 24/7.

Use the MCP as execution only — keep the brain outside the model

The strongest pattern among people reporting results: a deterministic, backtestable signal engine decides; the agent just places and manages the order via the MCP.

The flagship 185-comment build runs a Ruby + Intrinio opening-range-breakout engine; Claude does zero deciding — it fires orders because the MCP makes execution trivial vs. hand-coding Robinhood's API. Claimed 3/3 live winning days and an 18-month backtest of ~45% annualized / Sharpe ~2.07. His words: "I don't let AI make any decisions… I just use Claude to make the actual orders."

Why it's the best move: it sidesteps the two killers — token cost (the math runs in a script, ~$0 tokens on a Max sub) and LLM unreliability.

Bolt a real data source onto the MCP — alone it's too thin

Recurring finding: the MCP gives execution + your positions but not enough market data to trade well — "you really just want the APIs." What works:

• RH MCP + FinancialModelingPrep MCP → ask the agent to research upcoming earnings / recent news, then trade. Same author open-sourced a Robinhood MCP+CLI, rhood-rs.
• RH MCP + your own feed (Intrinio, ThetaPal) wired in through the script.
• Feed real numbers in explicitly — left alone the model will invent the data a formula needs from its training.

Make discipline a system — it's what people credit for not blowing up

• Cross-family red-team: Claude proposes, Codex (a different model family) tries to kill the trade before it's placed. Day one it caught that the next session was a market holiday and flagged a "sell-the-news" trap. Best add-on: log every veto + the counterfactual so you can measure whether the red-team adds edge.
• Scheduled agents: a morning research+trade run, a pre-close agent that enforces stop-losses, a weekly review. Cheap model for the grind, premium only on exceptions.
• Local always-on news watchdog (Gemma 4 in LM Studio) filters the firehose and escalates only material items — covering the fact the agent can't watch news live.
• Model proposes, human decides — or use AI only to verify / reject your own RSI-MACD-Bollinger signals. Set hard stops at the broker, not as AI alerts.

Pick the model for the job

• Execution reliability on Robinhood → Sonnet (thinking off helps it not refuse).
• Cheaper iteration → GPT-5.5 / Codex; Claude has better context but is token-hungry, which eats small-account profit.
• Counter-intuitive: don't dump historical data into the model — one builder found a small self-grown DB traded better than a big history dump.
• One data point on raw model skill (from a sim on a different broker, not Robinhood): GLM-5.2 and Gemini 3.1 Pro were the only two that stayed consistently profitable.

Log everything and benchmark against SPY

The setups that survive contact with reality write decisions to a SQLite log and run a plain SPY trade as the baseline — morning analysis (incl. Reddit sentiment via apewisdom), midday execution, end-of-day review. Judge on win rate over 30–100+ trades, max drawdown, Sharpe, and realistic slippage — never a two-day streak. The flagship's own admission: at 0.15% slippage its 45% backtest collapses toward 0%.

What the official app community (r/RobinhoodApp) adds

The Robinhood app's own subreddit — where staff like u/Robinhood_Alex actually reply — is the richest vein, and it shows the feature is not just day-trading bots:

• The most popular use is passive, not day-trading: people recreate M1-Finance-style automation — define a portfolio by percentages and have the agent add new money in those ratios and rebalance, "percentage-state aware."
• Options have landed (~12 Jun) via the MCP — chains, full Greeks, place/cancel.
• Same friction, louder: "I can't make it automated — it insists on a manual OK for everything" (Claude Pro), and there's still no paper-trading sandbox to practice in.
• The reality check: a "+2% in two weeks on $850" update drew "all that tax work for $18" and "my boring mutual funds are up 5.18% in the same window."
• A community "agentic trading challenge" lined up dozens of people's bot results side by side — a good place to eyeball what's actually happening.

Equities — and now options

At launch it was equities only, but as of ~12 Jun options are rolling out to agentic trading through the MCP — discover chains, pull full Greeks, and place or cancel orders. Crypto and futures still aren't supported, and reliability is shaky (users reported the app and agents going down mid-session, unable to close SPY puts).

The MCP is the only programmatic route

Robinhood still exposes no traditional REST API, so even non-AI bots have to talk to the MCP server to reach the account.

Isolated account, capped, approval-gated

Dedicated agentic account, separate from your portfolio; the agent reads all accounts but trades only in the agentic one; user-set spending cap; per-trade push approval; disconnect anytime. PDT being scrapped makes small-account experiments viable.