mcp-tool-cache-stale-after-mid-session-server-rebuild

When an MCP server is rebuilt and restarted mid-session, Claude Code’s tool cache retains the old tool names and signatures from session start. The new tools are correctly registered and callable via the server endpoint, but the in-session tool discovery reflects the pre-rebuild state. Verification of new tools must be done via docker exec or direct HTTP introspection of the MCP endpoint, not via Claude Code’s tool search. Cache refreshes only on new session start.

Related

• 2026-04-04-oracle-001-self-architecture-analysis
• salesforce-mcp-tools-absent-from-deferred-list-despite-regis
• openspace-mcp-global-registration-in-root-claude-json
• mcp-tool-namespace-discipline-fully-qualified-server-prefix
• salesforce-mcp-session-drop-requires-http-fallback
• mcp-tool-cache-stale-after-mid-session-rebuild
• mcp-server-tool-cache-stale-after-mid-session-rebuild
• mcp-tool-cache-stale-after-container-rebuild-in-same-session
• mcp-tool-cache-stale-after-mid-session-container-rebuild
• mcp-tool-cache-stale-when-server-rebuilt-mid-session