Simple one. The Linear MCP constantly switches from a green dot to a red dot. Once this happens, it is only a matter of (not all that much) time before the agent can no longer interact with Linear via the MCP. Further, when it stalls, it really stalls, the agent just hangs, never times out, never continues, it just stops, waiting for a response that will never come.
Steps to Reproduce
Install and configure Linear MCP.
Enable Linear MCP.
Use Linear MCP within Agent for a while.
Linear MCP eventually stops functioning (arbitrary.)
Weep as agent stalls indefinitely.
Disable Linear MCP.
Enable Linear MCP.
Prompt agent to try again (usually succeeeds.)
Expected Behavior
Linear MCP should not constantly drop out, and if it does, Agent should be able to identify that it is not getting a response, should be able to check the status of the MCP (i.e. is it configured properly, has the connection just failed or timed out, etc.), and figure out how to continue on its own (i.e. maybe retry a couple of times, then if that fails, alert the user that there is something wrong, PAUSE and wait for the user to fix things, maybe offering a button to continue and try again after user fixes issue)
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
This problem seems to be rather prevalent lately. I am often having to go into my cursor settings when a linear MCP call hangs, disable it, then renable it immediately, and hope that it starts up again before the agent retries the MCP command. MCP calls seem to hang a lot, and this is the only way I seem to be able to get the agent to re-try the call without otherwise disrupting work on the last prompt.
I have noticed that when an MCP call fails, and if you expand it you can clearly see details in the response json like error and other information that clearly denotes an error occurred, the MCP panel in the agent chat still gets a green checkmark, as if it succeeded. I think that if an MCP call fails, it should get a red X like other failed tool calls get.
I also noticed that, frequently, within seconds of disabling and re-enabling the Linear MCP in cursor settings, it will go yellow, then green once its ready…then within a few seconds will immediately go red. There is no information about why it goes to a red indicator, and the arbitrary nature of a red indicator makes it difficult to know if there is some kind of underlying issue with the MCP. The issues with the Linear MCP, though, have been persistent since I first started using it, but hangs while trying to invoke Linear MCP commands have become much more prevalent more recently.
It would be nice to have some insight into why the MCP is always in a red status/state, and whether that is leading to the issues I’m encountering actually using the MCP.
Want to add here…it seems there are many more MCPs that are going yellow or red now. Linear is the most problematic, and it may be due to their implementation (although I don’t think I’ve had the same problem with other agentic tools that use MCPs). I have noticed that my Supabase MCP configs (of which I have many for different environments) will often do the same thing…sometimes immediately after I enable them (and when I go to instruct the agent to use said Supabase MCP, it then fails.)
The Github MCP seems to have a fair amount of problems as well…and notably, that MCP has more commands than Cursor generally even allows anyway. Not sure if there is a better way of handling that.
I have also noticed that when I instruct the agent to check the MCPs, NONE of the core MCP-management commands that seem to exist in Cursor, actually work. There is a command to list the available MCPs for example…doesn’t work. Never, ever lists any MCPs. Even if I enable every one I have configured.
Seems there are some fairly extensive and fundamental bugs in your MCP system. I would put fixing this WAY after fixing @Docs, which I consider a VASTLY more important feature, but, it would be nice not to have to constantly fiddle with the MCP configs, and for the MCP system as a whole in Cursor, to work, wholly.