MCP Server doesn't update

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

After I change an MCP server (update tools, descriptions, etc.) it doesn’t update in Cursor. Even after I click Reload MCP Server or turn it off an on. It only updates when I restart Cursor.

Steps to Reproduce

I have a local MCP server. I update the code. And in cursor settings in Installed MCP servers it is not updated.

Operating System

Windows 10/11

Version Information

Version: 3.9.16 (system setup)
VS Code Extension API: 1.105.1
Commit: 042b3c1a4c53f2c3808067f519fbfc67b72cad80
Date: 2026-06-27T06:41:01.941Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey @Mike1111, this is a known MCP quirk, MCP needs their host to be rebooted most of the time if their file config is modified, that means restarting Cursor or the platform you are using them.

Then what does the “Reload MCP server” button do?

The Reload MCP Server button restarts the connection to your server (it stops it and launches it again). That’s useful when a server has dropped, crashed, or gotten into a bad state.

What it currently doesn’t do reliably is pick up new or edited tools and descriptions after you change your server’s code. It reconnects but keeps showing the previously loaded tool list, so your edits don’t appear, and toggling the server off and on has the same problem. This is a known issue our team is actively investigating.

@Tom_Coustols - is right that a full restart is the fix for now: fully quitting and reopening Cursor is the reliable way to get your updated tools to show up.

If you’re actively developing the server, one thing worth trying: if your MCP framework can emit a notifications/tools/list_changed message when its tools change, Cursor is designed to refresh the list live without a restart. A full restart is still the most dependable option today.

More on MCP setup: MCP docs

Ok, thanks for responding.