{"version":"2.1.282","anchor":"mcp-discovery-cache-is-forced-off-in-diskless-launches","canonical_anchor":"mcp-discovery-cache-is-forced-off-in-diskless-launches","heading":"MCP discovery cache stays off when Claude Code runs without a disk","tier":"notice","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/mcp-discovery-cache-is-forced-off-in-diskless-launches","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### MCP discovery cache stays off when Claude Code runs without a disk\n\nIn a diskless launch, Claude Code now keeps the MCP discovery cache off for the whole session regardless of other settings\n\n**Unclear.** How a user starts Claude Code in diskless mode is not known.\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools. Claude Code can keep a cache on disk of what it has discovered about them. When Claude Code is launched in diskless mode (with no disk storage available to it), that cache is now switched off for the rest of the session, whatever `MCP_DISCOVERY_CACHE` or the remote off switch says.\n\nPreviously the cache could only be forced off by `MCP_DISCOVERY_CACHE`, the remote off switch, or not being enabled.\n\n**Why**\n\nA machine with no disk should not try to read or write a cache that lives on disk.\n\n- Area: MCP\n- Names: `MCP_DISCOVERY_CACHE`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}