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

When an MCP server is rebuilt and restarted mid-session (e.g., replacing the entire Docker image), Claude Code’s tool cache continues to reflect the old tool names and schemas for the remainder of the session. New tools registered by the replacement server are not visible until the session is restarted. Verify the actual server’s tool list via docker exec or direct HTTP calls rather than trusting Claude Code’s cached tool list.

Related

• mcp-tool-cache-stale-after-mid-session-server-rebuild
• mcp-tool-cache-stale-after-mid-session-rebuild
• 2026-04-04-oracle-001-self-architecture-analysis
• salesforce-mcp-tools-may-not-appear-despite-permanent-regist
• docker
• mcp-tool-cache-stale-after-container-rebuild-in-same-session
• mcp-tool-cache-stale-after-mid-session-container-rebuild