Hey, thanks for the report. This is a known issue in version 2.3.41. MCP servers connect, but the agent can’t see them.
Alternative workaround (if you don’t want to roll back): open a new chat and ask the agent to list all available MCP tools. After that, it starts seeing them, but you’ll need to do this in every new chat.
The team is aware of this issue. I’ve added your reports to help increase visibility.
Using 2.3.41 with Opus 4.5 (also tried with Auto and Composer 1), I still have the tool discovery problem after trying your workaround. Interestingly, most tools are discovered and do work, however there’s a single tool in my MCP that refuses to function. I observe something interesting – in the MCP log, I see:
“2026-01-1816:37:04.030 [info] listResources: Found 0 resources
2026-01-1816:37:04.030 [info] Found 23 tools, 4 prompts, and 0 resources”
However, in the Cursor UI itself, I see “22 tools, 4 prompts enabled”.
My enviroment is as follows: “Version: 2.3.41
VSCode Version: 1.105.1
Commit: 2ca326e0d1ce10956aea33d54c0e2d8c13c58a30
Date: 2026-01-16T19:14:00.150Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Linux x64 6.8.0-90-generic”