Choose which Robinhood workflow you mean
NexusTrade stores a portfolio as explicit conditions and trading actions. Aurora can research a company, create the rules and submit historical backtests. A separate paper deployment records simulated behavior going forward. Python and TypeScript SDKs and MCP tools expose the same account workflow.
Robinhood Agents runs inside the Robinhood mobile app. It can research holdings and propose or place trades in a dedicated Agentic account. Trade approvals are on by default; eligible trades can execute without per-order approval when that setting is disabled. External agents use a separate Robinhood Trading MCP connection.
Compare the workflow
| Authoring | Aurora creates explicit portfolio rules | Native agent conversation and skills |
| Historical and paper evidence | Saved backtests and separate paper deployment | Native app research and brokerage actions; confirm the simulation workflow you need |
| Account actions | Select an eligible connected brokerage account for a live portfolio | Dedicated Robinhood Agentic account |
| External client | NexusTrade MCP with OAuth | Robinhood Trading MCP with separate authentication |
No matching rows. Clear the filter to see all records.
Connect Claude Code to both services
Use the command below for Robinhood, open /mcp in Claude Code, select robinhood-trading and authenticate. Add NexusTrade separately with its own server URL and OAuth. Ask for a read-only account summary from each server before proposing any trade.
Robinhood says external agents can read all connected Robinhood accounts but can place trades only in the Agentic account. Keep the server name and target account in each proposed action. Connecting both services does not transfer a NexusTrade strategy into Robinhood native Agents.
claude mcp add robinhood-trading --transport http https://agent.robinhood.com/mcp/tradingWho each route may suit
Choose native Robinhood Agents when you want an assistant inside the brokerage app and its dedicated-account controls. Choose NexusTrade when your work centers on inspectable strategy definitions, historical experiments, paper observation and developer access.
For Claude Code research, you can use both MCP connections in one workspace. Review the sources and strategy configuration in NexusTrade, then treat a Robinhood brokerage action as its own account decision.
Try a research task before choosing execution
Ask for the reporting period and primary sources behind one company thesis. Keep the output separate from a trade proposal. Next, define the rule you would test and check that its timing, sizing and exits can be represented in the platform you choose.
Costs, account eligibility and comparison scope
Check the current subscription, compute charges, brokerage fees, supported country and account permissions for the workflow you intend to use. A platform capability does not establish that your account can trade a particular instrument.
This comparison describes workflows checked October 10, 2026. We have not run matched strategies or live accounts across the products, so it contains no ranking of returns, fill quality or execution speed.
Check a missing tool or failed account read
If a read fails, check the named server and complete its authentication in /mcp before retrying. Confirm which service returned each account and its identity. An account from NexusTrade and an account from Robinhood are separate records; do not treat discovery of both servers as authorization for a brokerage action.