GROK BOT / connect-robinhood-agentic-trading-mcp-in-grok-bot

Grok Bot

Connect Robinhood Agentic Trading MCP in Grok Bot

Connect Robinhood Agentic Trading MCP in Grok Bot

Robinhood’s public Agentic Trading MCP is a custom remote at https://agent.robinhood.com/mcp/trading. OAuth can fail with oauth/error after Allow, especially when the callback looks like grokbot://mcp/oauth/callback or the Allow step takes too long. Staff (deanrie, Sep 9, 2026 on forum 171111) gave the working path below. Broker redirect bugs that never open HTTPS (IBKR-style) are a different post: Fix custom MCP OAuth redirect_uri failures in Grok Bot.

Add the MCP

  1. In Grok Bot, open Plugins / Connectors and add a custom remote MCP.
  2. Paste:
https://agent.robinhood.com/mcp/trading
  1. Start Authenticate when the connector shows needsAuth / 0 tools.

Finish Allow inside the window

Staff: since 7 Sep 2026 the callback Cursor expects is a normal https://www.cursor.com/agents/... URL (not grokbot://). The authorize token is short-lived (~15 minutes). If you authorize Robinhood but Cursor only receives the callback ~17 minutes later, it rejects the grant as expired and you land on oauth/error.

  1. Approve the Robinhood device / login prompt first if Robinhood asks.
  2. Tap Allow on the Cursor/agents page within a couple of minutes — do not leave the flow open while you do something else.
  3. Return to Grok Bot and confirm the connector leaves needsAuth and lists tools.

Prefer desktop once, then use phone

Connectors are account-scoped. Staff’s most reliable path: complete OAuth once from Grok Bot desktop or Cursor on the same account, then use the phone after the account already holds the grant. Re-trying only on mobile after a slow Allow often repeats oauth/error.

If it still fails

  • Paste the full authorize URL and the time you hit Allow into the forum thread (or a new reply on 171111).
  • Clear a hung custom remote and re-add: Clear hung custom MCP remotes in Grok Bot.
  • Confirm trades inside Robinhood’s own UI — MCP tools do not replace broker confirmation.

Pitfalls

  • Treating a grokbot:// callback screenshot from an older attempt as today’s expected URL — staff say the live callback is https://www.cursor.com/agents/....
  • Starting Authenticate, approving Robinhood, then waiting past ~15 minutes before Cursor finishes the agents Allow page.
  • Confusing this with Zoom localhost:4700 or IBKR redirect_uris HTTPS/loopback failures — those are separate fix posts.