Linear MCP commonly errors out and requires turning off then on

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

So, whenever, so I have the linear MCP installed and I find that after a little while the linear MCP will complete the error out making it unusable in Cursor. I have to go to the settings and then turn it off and then turn it back on and it reconnects properly but there seems to be some bug here where the linear MCP errors out in the background.

2026-01-13 16:16:42.900 [info] Handling ListToolsRaw action

2026-01-13 16:16:42.900 [info] Handling ListToolsRaw action

2026-01-13 16:16:42.900 [info] Handling ListToolsRaw action

2026-01-13 16:16:42.900 [info] Handling ListToolsRaw action

2026-01-13 16:17:15.869 [error] Client error for command SSE error: undefined

2026-01-13 16:17:15.893 [info] Handling ListToolsRaw action

2026-01-13 16:17:15.894 [info] Handling GetInstructions action

2026-01-13 16:17:15.895 [info] Handling GetInstructions action

Steps to Reproduce

  1. Connect linear MCP
  2. Wait 1 hour
  3. Try to access a tool in the linear MCP via an agent
  4. See that the linear MCP has an error and has to be turned off and then on again.

Expected Behavior

Once I’ve connected the MCP, it should be a valid configuration until I disconnect it. I shouldn’t have to routinely turn it off and then turn it on.

Screenshots / Screen Recordings

CleanShot 2026-01-13 at 16.19.55
CleanShot 2026-01-13 at 16.19.55684×452 11.8 KB

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.35 (Universal)
VSCode Version: 1.105.1
Commit: cf8353edc265f5e46b798bfb276861d0bf3bf120
Date: 2026-01-13T07:39:18.564Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.2.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

MCP servers disconnect repeatedly - "Not connected" error
4

Hey, this is a known issue with SSE connections for MCP servers: the OAuth token expires, and the auto-refresh doesn’t kick in.

The team’s already aware and is tracking it. Similar reports have been discussed here: Remote MCP connections fails every few minutes

For now, the workaround is the same as yours: toggle it off and on in Settings. Unfortunately, there isn’t a cleaner fix yet, but a proper fix is in progress.

1 Like