After MCP Authorization GUI still report an error

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

And here we continue Remote MCP server on localhost fails
because it was auto closed y the nasty bots which have no idea what they are doing, and the issues was still not resolved but the bot didn’t care.

Here is the video. clearing through the agent works but

  1. Still no button to clear (very annoying) tokens for a specific MCP server session
  2. Need to exit cursor after clearing by the agent to really clear the clearing of the clearing
  3. Cannot clear access tokens for a specific MCP server
  4. Attached video. After switching to another selection form the Menu, the connection is green

both the proxy and direct use the same MCP server uri.

Steps to Reproduce

See video

Expected Behavior

Green (Connected) status after OAUTH2 cycle

Screenshots / Screen Recordings

Operating System

Linux

Version Information

Version: 3.2.21
VSCode Version: 1.105.1
Commit: 806df57ed3b6f1ee0175140d38039a38574ec720
Date: 2026-05-03T01:46:14.413Z
Layout: glass
Build Type: Stable
Release Track: Nightly
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Linux x64 7.0.3

For AI issues: which model did you use?

N/A

For AI issues: add Request ID with privacy disabled

N/A

Additional Information

N/A

Does this stop you from using Cursor

No - Cursor works, but with this issue

6

Hey, thanks for following up with the video thread, it helps. I’ll go point by point:

Per-server token clear / Clear All MCP Tokens
The Clear All MCP Tokens command still exists. You can access it via Cmd+Shift+P or Ctrl+Shift+P then MCP: Clear All MCP Tokens. Per-server clear without all is a valid feature request, we don’t have a separate button for a specific server right now.

Required restart after clear
That’s a known limitation. Tokens are cached at runtime, and without reloading the server they won’t be picked up. It’s on our radar under MCP reliability, no ETA yet.

Status stays error after successful OAuth, only turns green after navigating
This sounds like stale UI state after the OAuth callback. The symptom matches a pattern we recently fixed on another surface in Glass. It’d help if you could:

  • Check if it reproduces in the Stable build, not Nightly, and confirm if yes.
  • Share the exact MCP server URI if it’s not private, or a minimal repro so we can test on our side.
  • If you see any errors or warnings in DevTools during the OAuth callback, please share them. Path is Help -> Toggle Developer Tools -> Console.

Nightly plus Glass tends to have more bugs in this area than Stable for now, just a heads up.