Describe the request
Feature Request: Clear MCP Tool Cache / Force Refresh
Problem
When developing MCP servers, Cursor appears to cache the available tools. After changing tool definitions (adding, removing, or modifying tools), Cursor often continues to show the previous versions.
Common attempts such as:
- Reload Window
- Developer Reload
- Disable/Enable MCP Server
do not always force Cursor to reload the tool definitions.
As a result, it is difficult to know whether Cursor is using the latest version of the server or a cached copy.
Proposal
Provide one or more of the following:
- Clear MCP Tool Cache
- Force Reload MCP Tools
- Refresh Tool Definitions
Ideally this could be available from:
- the MCP Server context menu
- the Command Palette
- or as a button in the MCP Server UI
Expected Behavior
After triggering the action:
- all cached tool definitions are discarded
- Cursor reconnects to the MCP server
- all tools are reloaded from scratch
- removed tools disappear immediately
- renamed or modified tools are refreshed
- newly added tools become available
Why this matters
When developing MCP servers, rapid iteration is essential. Developers frequently modify tool schemas, descriptions, and capabilities.
Without a guaranteed cache refresh, it’s impossible to know whether a test is exercising the current implementation or stale cached metadata.
Having an explicit Force Refresh or Clear Cache command would make MCP development significantly more reliable and reduce time spent debugging caching issues instead of the server itself.
Operating System (if it applies)
MacOS