Hey, thanks for the report. There are a few known issues with MCP tool detection that the team is working on. Some are already fixed, and some are still being tracked.
To understand what’s happening in your case, I’ll need a few details:
- Which MCP servers are being ignored? Please share the names and types of your custom MCPs.
- What status do they show in Cursor Settings > Tools & MCP, green, yellow, or red?
- Where are they configured, at the project level in
.cursor/mcp.json, or in global settings? - One concrete example: what did you ask the agent to do, and what did it do instead of calling your MCP tool?
- A Request ID from one of those chats (top-right menu in the chat > Copy Request ID).
Also, did you try turning the affected MCP servers off and back on after updating to 2.5.17? Similar reports were fixed by re-enabling the servers.
Related thread with a similar issue: The Agent cannot access the MCP Servers configured in Cursor Settings The Agent cannot access the MCP Servers configured in Cursor Settings
Let me know. Once I have a Request ID, I can dig in more.