TL;DR
This Robinhood workflow uses Claude Code with separate NexusTrade and Robinhood MCP connections. NexusTrade supplies saved research and paper evidence; Robinhood supplies brokerage account tools. Enable Robinhood's external-agent trade approvals, inspect the proposed account and order, then verify its actual status. A paper portfolio does not automatically execute through Robinhood, and ongoing operation needs an explicit schedule. Stop the external executor separately and review open orders and holdings.
Follow one worked path
Connect both MCP servers
Set up NexusTrade and Robinhood as separate Claude Code MCP servers using the instructions below. Complete each server's account authorization.
NexusTrade Claude Code setupRead the connected account identity before changing a saved strategy or preparing an order.
claude mcp add --transport http nexustrade https://nexustrade.io/api/mcp
claude mcp add robinhood-trading --transport http https://agent.robinhood.com/mcp/trading
Review the tested candidate
Inspect the saved rules, historical test and separate paper observation. Verify target account and applicable trading permissions.
The intended strategy and broker account are identified; simulation history is not a broker fill.
Review the external-agent order path
Keep Robinhood's external-agent approvals enabled. Review the proposal and account details before approving an order through that server.
Two connected servers do not create a synchronized persistent executor. An accepted order is not necessarily filled.
Verify and pause the correct executor
Inspect broker order state and account activity. Stop the external executor separately from any NexusTrade portfolio.
Pausing an executor does not automatically sell holdings or cancel outstanding broker orders.
Inspect the full illustrated deployment sequence
Follow one reviewed strategy into Robinhood
Show the table · 5 rows, 2 columns
| Step | Artifact to inspect |
|---|---|
| Connect both MCP services | NexusTrade research tools and the separate Robinhood connected account. |
| Review candidate and account | Exact saved rule version, allowed asset and available buying power. |
| Review a proposed order | Broker trade approvals, ticker, side, quantity and account before execution. |
| Inspect returned order status | Broker order ID and actual state; submitted or pending does not establish a fill. |
| Stop the executor | Pause or revoke the external agent separately from a NexusTrade portfolio. |
No matching rows. Clear the filter to see all records.
This resource follows the direct external-client Robinhood MCP workflow. Keep the saved NexusTrade research candidate separate from the Robinhood execution account. The native NexusTrade connection is a different path, linked below.
Research in NexusTrade, execute through Robinhood MCP
Show research in nexustrade, execute through robinhood mcp
This workflow uses Claude Code with two separately authenticated servers: NexusTrade for saved strategies and historical or paper evidence, and Robinhood Trading MCP for its brokerage account tools. NexusTrade also supports a native Robinhood connection in its broker picker; this guide covers the external-agent path where Claude Code drives both servers.
Keep the NexusTrade portfolio ID and Robinhood account ID separate. A NexusTrade paper deployment does not automatically run the same rule in Robinhood. Claude Code also needs an explicit execution schedule if you want ongoing operation after a conversation ends.
Start with a saved, tested candidate
Show start with a saved, tested candidate
Write explicit entry, sizing and exit rules, then save the strategy. Fix the historical test period, capital and benchmark before running it. Review warnings and individual orders as well as the return curve.
Use a separately identified NexusTrade paper deployment to observe simulated operation before brokerage deployment. Retain the original saved candidate ID, backtest ID and deployed paper ID. A backtest curve is not paper history, and paper results are not live fills.
Connect both MCP servers in Claude Code
Show connect both mcp servers in claude code
Run the two commands below. In Claude Code, enter /mcp, select each server and complete its browser authentication. Robinhood prompts eligible users to open a dedicated MCP account during onboarding. Confirm the target account before continuing. Follow Robinhood's external-agent onboarding for eligibility and account setup.
claude mcp add --transport http nexustrade https://nexustrade.io/api/mcp
claude mcp add robinhood-trading --transport http https://agent.robinhood.com/mcp/tradingTurn on Robinhood trade approvals first
Show turn on robinhood trade approvals first
Robinhood documents trade approvals as off by default for external MCP accounts, while built-in agents default to on. In the Robinhood app, select your MCP account → connected agent → Agent Settings → Safety Controls → Trade approvals, then turn them on. When enabled, review and manually place proposed orders in the app. See Robinhood's trade approval controls before the first order proposal.
Use get_trade_approval_setting to read the setting and get_accounts plus get_portfolio to check the account and buying power. Discover the current input schemas rather than borrowing NexusTrade parameters. These are Robinhood tools, even where a tool name resembles a NexusTrade tool.
Prepare an execution plan from the reviewed rules
Inspect the request
Ask Claude to read the exact NexusTrade candidate and paper evidence, then translate the next eligible action into a Robinhood proposal. Review the account, symbol, direction, size, order type and limit before placing anything. Strategy evaluation timing and broker order submission are different parts of the workflow.
Require explicit approval for the first execution step. Do not interpret a backtest result or an MCP connection as permission to trade.
Read my selected NexusTrade strategy and its paper results. Read the Robinhood MCP account and trade-approval setting. Draft the next eligible order with account, symbol, side, size and order type. Show any differences from the tested rules. Stop for my review before submitting or scheduling anything.Check orders and stop the right executor
Show check orders and stop the right executor
Robinhood shows agent orders in the MCP account Activity and Robinhood history. Inspect pending approvals and actual order state; a proposal or accepted order is not proof of a fill. Preserve the broker order identifier separately from the NexusTrade portfolio and backtest IDs.
If you add recurring execution, document its owner, cadence and stop control. Stop that agent or schedule, then inspect open orders and positions in Robinhood. Turning off a NexusTrade paper portfolio does not stop a separate Robinhood executor. Keep brokerage trade approvals on while reviewing changes.
No comments yet.