MCP Server Cache Not Refreshing After Rebuild

Resolved 💬 5 comments Opened Jul 7, 2025 by cfdude Closed Jan 8, 2026

Bug Description
If you are using Claude Code to work on or build an MCP server that is also loaded into Claude Code. If you rebuild that mcp server 'npm run build' for example, it will rebuild the server and the code changes will be in the local file system but Claude Code hangs onto some kind of cache of the mcp server that prevents it from seeing the updates despite the server restarting. This forces users to exit the claude code session and then come back with 'claude --continue' just to have the MCP cache refreshed and see the new changes. Claude Code should have it's own way to clear or reload that mcp cache that isn't reliant on exiting a session or having a human use some kind of /mcp command.

Environment Info

  • Platform: darwin
  • Terminal: vscode
  • Version: 1.0.43
  • Feedback ID: 5cb0a268-2b1f-458e-afb4-f79a00e73133

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗