{"version":"2.1.286","anchor":"mcp-auto-discovery-disabled-when-a-new-check-is-true","canonical_anchor":"mcp-auto-discovery-disabled-when-a-new-check-is-true","heading":"Automatic MCP server discovery has one more condition that can switch it off","tier":"notice","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/mcp-auto-discovery-disabled-when-a-new-check-is-true","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Automatic MCP server discovery has one more condition that can switch it off\n\nAutomatic discovery of MCP servers now also stays off when an additional check at the start of its conditions is true\n\n**Unclear.** What the new first check tests is not known, so it is unclear when it turns automatic MCP discovery off.\n\n**What**\n\nMCP (Model Context Protocol) is the way Claude Code connects to outside tools and data sources, called MCP servers. Claude Code can find some of these servers automatically. Whether it does depends on a list of conditions, including the `mcpAutoDiscovered` policy setting and not running under HIPAA or zero data retention arrangements.\n\nThat list now starts with one more check. When that check is true, automatic MCP discovery is off, whatever the other conditions say.\n\n**Why**\n\nThis adds another way for automatic MCP discovery to be suppressed, on top of the managed policy setting and the other existing conditions.\n\n- Area: MCP\n- Names: `mcpAutoDiscovered`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}