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

When an MCP server container is rebuilt mid-session, Claude Code’s tool cache retains the old tool names and schemas for the remainder of that session. The new tools are only discoverable after session reconnect. To verify new tool schemas without reconnecting, use docker exec <container> python -c 'import json; ...' or call the server’s MCP initialize handshake directly via curl against the streamable-http endpoint.

Related

• docker
• mcp-tool-cache-stale-after-mid-session-server-rebuild
• notebooklm-mcp-streamable-http-returns-sse-not-json
• mid-session-claude-mcp-add-s-project-doesn-t-load-tools
• salesforce-mcp-tools-absent-from-deferred-list-despite-regis
• 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
• vault-mcp-client-cannot-reconnect-mid-session-use-filesystem