UI shows wrong MCP server status

[aurafriday (Chris)]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The UI says “error”, when there is no error (agents can still use the tools, and the log shows everything is normal).

Steps to Reproduce

Use some non-stdio MCP servers in windows. Turn it off and on again, and the UI shows the right status then.

Expected Behavior

The UI should reflect the actual MCP server state

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.4.7 (user setup)
VSCode Version: 1.105.1
Commit: ca0f9bf806f235ea014a22712cbcbf5e88ca77e0
Date: 2026-01-20T20:52:38.077Z
Build Type: Stable
Release Track: Early Access
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26100

Additional Information

This is a first-time new report for just this bug - you have dozens of other unfixed MCP server bugs, and this has been mentioned in those reports before, but never as a bug in its own right.

Does this stop you from using Cursor

No - Cursor works, but with this issue

[aurafriday (Chris)]

If you click the on/off

and turn if off

It turns off

and then when you turn it back on again, it reconnects - the logs show the same as when the IDE wrongly said “error”

but the IDE now shows the correct status.

[deanrie]

Hey, thanks for the report. This is a known issue. The UI doesn’t update the status after a successful MCP server reconnection, even though everything works fine. We got the exact same report yesterday: MCP Server: Red error dot persists after successful reconnection - UI state not cleared

The team is aware and working on a fix. For now, the workaround is to toggle it off and on in settings, which you’re already doing.

This happens on both Windows and macOS, so it’s not platform-specific.