Card #343 · Cursor (AI IDE)
MCP OAuth authentication failures and host instability
Merchants are experiencing significant issues with MCP OAuth flows, including failed browser redirects, 'Forbidden' errors, and authentication loops. On Windows, stale OAuth records can completely wedge the MCP host, causing all servers to fail regardless of their configuration.
Pain score
0.25/ 1.00 · weighted product of four components
Reach1.00distinct authors (log-normalized)
Recency1.00freshness decay, half-life months
Engagement0.99upvotes + comments, normalized
Monetization0.50willingness-to-pay cues in evidence
§ Evidence — 5 verified quotes
On Windows, every MCP server in Settings → MCP shows “Error” — including pure-local stdio servers that use no OAuth and no network.
stale OAuth-attempt records left behind by a previously failed MCP OAuth flow wedge the entire MCP host initialization on startup, so ALL servers go down regardless of transport.
Adding the official Figma MCP ( https://mcp.figma.com/mcp ) in an Automation’s Tools tab immediately shows a red “Forbidden” badge. No browser redirect to Figma ever opens, so the OAuth flow fails before authorization.
Robinhood MCP OAuth fails in Cursor CLI during the authorize step. The IDE auth flow for the same server works.
Using MCP with Oauth even though its configured and authenticated with Cursor App - is not working - it errors saying “Local SDK runs cannot request interactive approval”.
Comments are a Pro feature — join the conversation, share what you've shipped, hear what others are building.
Upgrade to Pro