Hey, thanks for the detailed report. This is a known CLI limitation, not something specific to Robinhood.
What’s happening:
The CLI uses the loopback redirect URI http://localhost:8787/callback, while the IDE uses a different callback mechanism, a deeplink like cursor://.... Robinhood’s OAuth server accepts the IDE option, but rejects the CLI loopback one. That’s why you see a 403 on authorize and a redirect to robinhood.com/oauth/error. So the same server can log in from the IDE, but fails via agent mcp login.
We saw the exact same pattern with Slack MCP in the CLI. Details here: Slack MCP: CLI login fails — redirect_uri mismatch (localhost:8787). Some fixes around redirect URI reordering have already shipped, but for providers that don’t allowlist loopback addresses, this still happens. This is a known issue and it’s being tracked, but I can’t share an ETA for Robinhood.
What you can do right now:
The IDE path still works, auth for this server succeeds there.
If Robinhood supports MCP via stdio or a token flow without an OAuth redirect, that transport is stable in the CLI since it fully avoids the loopback flow.
If I have an update on a fix, I’ll post it in the thread.
Robinhood has officially listed Cursor as a supported platform, alongside Claude, ChatGPT, and Codex, so it’s not that they don’t know about Cursor. The gap is specifically on the Cursor CLI side.
What happens in practice: Claude Code and the Codex CLI successfully complete Robinhood’s loopback OAuth flow. Claude uses a random ephemeral port, Codex uses a fixed one, default 1455. Cursor CLI sends a fixed localhost:8787/callback and gets a 403 on authorize. Since Cursor is officially supported and the IDE path works, this is a CLI-side limitation on our end, not something Robinhood needs to fix.
So reaching out to Robinhood is probably not the right lever. The fix needs to come from Cursor CLI. I can’t share an ETA yet, but I’ll post an update in the thread as soon as I have one.
For automation in the meantime, your options are the IDE path, since auth works there, or, if Robinhood supports a stdio flow or a token-based flow without an OAuth redirect, that transport is stable in CLI because it fully avoids loopback.
I successfully connected robinhood on one machine via IDE but I am getting this same error on another now and can’t connect it. I am using the cursor ide not the CLI.
{“detail”:“Mismatching Redirect URI: http://localhost:8787/callback”}