{"version":"2.1.319","anchor":"mcp-debug-log-skipping-now-read-from-a-store-value","canonical_anchor":"mcp-debug-log-skipping-now-read-from-a-store-value","heading":"Skipping MCP debug log files no longer reads its environment variable directly","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/mcp-debug-log-skipping-now-read-from-a-store-value","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Skipping MCP debug log files no longer reads its environment variable directly\n\nThe check that skips per-server MCP debug log files now reads a stored value instead of reading CLAUDE_CODE_SKIP_MCP_DEBUG_LOG_FILES directly\n\n**Unclear.** Whether setting CLAUDE_CODE_SKIP_MCP_DEBUG_LOG_FILES still turns this behaviour on is not clear.\n\n**What**\n\nThe check that decides whether to skip writing a separate debug log file for each MCP server has changed. It no longer reads the `CLAUDE_CODE_SKIP_MCP_DEBUG_LOG_FILES` environment variable directly. It now reads a stored value tied to the piece of work currently running. The environment variable is still used elsewhere in Claude Code.\n\n**Why**\n\nSkipping these files may now apply to one part of the work at a time rather than to the whole Claude Code process.\n\n- Area: MCP\n- Names: `CLAUDE_CODE_SKIP_MCP_DEBUG_LOG_FILES`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}