{"version":"2.1.271","anchor":"mcp-config-read-failures-now-distinguish-an-inaccessible-par","canonical_anchor":"mcp-config-read-failures-now-distinguish-an-inaccessible-par","heading":"MCP config read failures now distinguish an inaccessible parent directory from a real read failure","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/mcp-config-read-failures-now-distinguish-an-inaccessible-par","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### MCP config read failures now distinguish an inaccessible parent directory from a real read failure\n\nMCP config read failures now distinguish an inaccessible parent directory from a genuine read failure\n\n**What**\n\nWhen Claude Code tries to read an MCP configuration file and the attempt fails with an EACCES error (permission denied) on a stat-type check, on non-Windows systems, it's now recognized as meaning a parent directory isn't searchable, rather than a real failure to read the file. In this case the config is reported as not present, with a distinct telemetry reason, instead of being logged as a generic fatal read failure.\n\n**Why**\n\nThis avoids treating a permissions quirk in a parent directory as a broken or corrupted MCP configuration, giving more accurate diagnostics when a config simply isn't reachable.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}