MCP Server: Red error dot persists after successful reconnection - UI state not cleared

[sag1v (Sagiv ben giat)]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When an MCP server restarts, Cursor successfully reconnects and retrieves tools (visible in logs: “Found 7 tools”), but the UI continues to show a red error dot with “Error - Show Output” status. The error state from the disconnection is never cleared, even though the connection is fully functional.

Steps to Reproduce

1. Configure a remote MCP server using Streamable HTTP transport
2. Start the MCP server locally
3. Connect Cursor to the MCP server - observe green status, tools loaded successfully
4. Stop the MCP server (Ctrl+C)
5. Observe Cursor shows red error dot (expected at this point)
6. Restart the MCP server
7. Wait for Cursor to reconnect (check Output panel - shows “Found 7 tools”)
8. Observe: UI still shows red error dot despite successful reconnection

Workaround: Manually toggle the MCP server off/on in Settings to clear the error state.

Expected Behavior

After successful reconnection (when “Found 7 tools” appears in logs), the UI should:

• Clear the red error dot
• Show green/healthy status
• Display the available tools

Instead, the error indicator persists even though tools are functional.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.41
VSCode Version: 1.105.1
Commit: 2ca326e0d1ce10956aea33d54c0e2d8c13c58a30
Date: 2026-01-16T19:14:00.150Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0

Additional Information

MCP Output logs showing the issue:

// Initial connection OK
11:39:44 [info] Successfully connected to streamableHttp server
11:39:44 [info] Found 7 tools, 0 prompts, and 0 resources

// Server stopped - error expected
11:41:51 [error] Client error for command fetch failed
11:41:51 [info] Found 0 tools, 0 prompts, and 0 resources

// Server restarted - reconnection successful but UI still red
11:46:52 [info] Connected to streamableHttp server, fetching offerings
11:46:52 [info] Found 7 tools, 0 prompts, and 0 resources ← SUCCESS but UI shows error!

Related issues:

• GitHub #3640: Cursor does not handle invalid session ID after MCP reconnect
• GitHub #3907: Remote MCP Server Shows “Error” on Startup Despite Successful Connection
• GitHub #3211: MCP Disconnection After Kill Tasks Need Refresh Button

This affects development workflows where MCP servers are frequently restarted.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

[deanrie]

Hey, thanks for the detailed report with logs and repro steps. This really helps.

This is a known issue with UI state management for MCP servers. After a reconnect, the UI doesn’t refresh the status, even when the server connects successfully and the tools are loaded. The team is aware and working on a fix.

Your workaround (toggling it off and on in Settings) is currently the best way to quickly clear the error state.

[sag1v (Sagiv ben giat)]

@deanrie
Thanks for the quick reply
Is there a way to track the progress on this fix? Maybe a public GitHub issue or something similar?

[deanrie]

Unfortunately, there’s no public way to track progress on this fix.

But I’ll let you know as soon as it’s fixed.