hey folks! im iterating on an mcp server, and having my cursor agent it test itself.
the problem im running into is cursor’s tool list cache remains stale as my tool list changes (new tools added, old tools updated).
the typical workaround i see people doing is creating a dedicated tool called list_tools() and then call_tool() which comes with the downside of side skirting any sort of built-into-harness safety/tool use confirmation measures.
asking the agent to just re-authenticate that mcp server doesn’t refresh the cache either.
Hey, thanks for the report. This is a known issue that we’re tracking, and I’ve added your case to it.
After Cursor loads a server’s tool list once, a reconnect like Reload, toggling it off and on, or signing in again reuses the cached list instead of making a new request to the server. That’s why re-authenticating doesn’t help. It’s just a reconnect. Fully quitting Cursor, with all windows closed, clears the cache.
There are 2 ways to get a fresh tool list without restarting:
Slightly change the server entry in mcp.json each time the tools change. Cursor treats the changed entry as a new server and reloads the tools from scratch. For a command-based stdio server, it’s enough to bump a dummy env variable:
"env": { "MCP_REV": "2" }
For a URL-based server, add or bump a dummy header, for example "headers": { "X-Mcp-Rev": "2" }. If the server uses sign-in, you may need to sign in again after the change. The agent can make this edit itself as part of the test cycle.
Have the server send notifications/tools/list_changed while Cursor is connected, for example right after the tool set changes. Cursor should reload the tool list when it gets that notification.
About list_tools() and call_tool(), you’re right. That approach bypasses the harness checks for tool confirmation, so I wouldn’t recommend it.
If neither option picks up the new tools, send over your Cursor version from Cursor > About and the server type, stdio or URL, and I’ll dig deeper.