mcp-tool-cache-stale-after-mid-session-container-rebuild
When a Docker container for an MCP server is rebuilt mid-session, Claude Code’s tool cache still reflects the old tool names and signatures from session startup. The new tools (38 in this case) are registered on the server but not visible to Claude Code until the session reconnects. Verification must use docker exec or direct MCP protocol queries rather than relying on Claude Code’s cached tool list.
Related
- mcp-tool-cache-stale-after-container-rebuild-in-same-session
- mcp-server-tool-cache-stale-after-mid-session-rebuild
- 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
- mcp-tool-cache-stale-when-server-rebuilt-mid-session