Describe the Bug
Same as this bug: Cursor v1.3 not detecting mcp tools
Cursor should NOT be discarding all the tools it was just given via “tools/list” after it tries a “prompts/list” against a server without prompts.
Steps to Reproduce
Use any MCP server without the prompts/list implemented.
Expected Behavior
Ignores any errors form the “prompts/list” method
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.4.0 (user setup)
VSCode Version: 1.99.3
Commit: 2cdf414b520ff31ee87dd841a04d8aa84009eae0
Date: 2025-08-05T23:10:54.574Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.17763
Additional Information
The workaround in Cursor v1.3 not detecting mcp tools should not be marked as a solution - Cursor still has the bug, and it makes no sense to expect millions of MCP servers to add a “do nothing” function for a feature they don’t support, just so cursor goes back to working OK like it used to.
Does this stop you from using Cursor
No - Cursor works, but with this issue