I’m writing this not out of contempt for Cursor or the team building Cursor but I am running into issues that cant be ignored.
My question, Is the implementation of MCP in Cursor Half-Baked. As I have been building out my project and trying to get into a workflow I have found that certain MCP servers are working well. Some MCP servers don’t even want to make an implementation of MCP for Cursor. That’s cool. I can write my own but man thats a drag.
One example is the Svelte Docs server. The guy developing this just threw up his hands and said the MCP implementation of MCP in Cursor was a “hot mess”
I am an early adopter so of course i update today to the bleeding edge 0.47.6 and the LLM no longer recognizes the tools it has access to.
So again my question is, what’s going on with the Cursor MCP Server Implementation?
Note: I am a PRO SUBSCRIBER & PAY $60 / Month. ( Most times I end up paying more)
===SYSTEM INFO===
Version: 0.47.6 VSCode Version: 1.96.2 Commit: 6a1a6fbc55483584e7022f491c8a167ccac86f20 Date: 2025-03-17T06:09:01.591Z Electron: 32.2.6 Chromium: 128.0.6613.186 Node.js: 20.18.1 V8: 12.8.374.38-electron.0 OS: Darwin x64 23.6.0
============AUTOMATED MESSAGE============
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.