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. Native Robinhood connection is currently hidden in NexusTrade's broker picker. Use the external-agent path described here.
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
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
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.
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
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.
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
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
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.