Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
Continues the symptom previously reported in the now-closed threads:
Reproducing on the latest stable, post the 3.3 MCP auth changes (“explicit stale token cleanup on re-auth” / “transient 401 handling and stale credential behavior”):
Need to click “Connect” / re-auth on at least one OAuth MCP every day, sometimes more
Reconnecting in window A does not propagate to windows B/C/D — each window can independently flip back to “Needs login”
mcp.json configuration syncs across windows fine; only the OAuth token store seems unsynced
stdio MCPs and bearer-token MCPs (static Authorization header in mcp.json) are unaffected — points at the OAuth token lifecycle, not transport
Steps to Reproduce
Configure an OAuth-style remote MCP server (GitHub, Notion, Linear, Atlassian, Vercel, etc.) via mcp.json
Open ~4 Cursor windows
Use Cursor over the course of a day
Within 24h, at least one OAuth MCP shows “Needs login” in at least one window
Expected Behavior
Cursor uses the refresh token returned by the MCP server’s /token endpoint to silently rotate the access token, instead of falling back to interactive auth
Single shared OAuth token store across all Cursor windows on the same machine
Operating System
MacOS
Version Information
Version: 3.3.30 Commit: 3dc559280adc5f931ade8e25c7b85393842acf30 Date: 2026-05-09T18:28:42.332Z Electron: 39.8.1
Does this stop you from using Cursor
No - Cursor works, but with this issue