My internal load balancing setup uses cookies to designate sticky sessions with the actual backend servers. If I test my SSE based MCP server deployment on something like postman where I can have set-cookie be respected across multiple http calls then I have no problem receiving data on the SSE session stream while sending messages, but on cursor the header set-cookie doesn’t seem to be getting used in the SSE client so there is no way to provide a sticky connection that let’s me keep communicating with the server that I have opened my SSE session stream on.
This should be fixable in the client by adding a set-cookie header to the /sse opening request of the MCP client.
Thanks for reporting a bug you have found in Cursor!
Please add the following info to help us diagnose your issue:
Check the forum to ensure the issue hasn’t been reported already
Provide a clear description of the bug
Explain how to reproduce the bug (if known)
Attach screenshots or recordings (e.g., .jpg, .png, .mp4).
Tell us your operating system and your Cursor version (e.g., Windows, 0.x.x).
Tell us if the issue stops you from using Cursor.