{"version":"2.1.273","anchor":"connector-disable-check-now-also-consults-a-second-source-e","canonical_anchor":"connector-disable-check-now-also-consults-a-second-source-e","heading":"Connector-disable check now also consults a second source (e4)","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/connector-disable-check-now-also-consults-a-second-source-e","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Connector-disable check now also consults a second source (e4)\n\nWhether claude.ai connectors are disabled is now checked against a second settings source too\n\n**What**\n\nThe check that decides whether claude.ai connectors (MCP integrations fetched from claude.ai) are disabled previously looked at only one settings source. It now also checks a second, new source, and connectors are treated as disabled if either source sets `disableClaudeAiConnectors` to true.\n\n**Why**\n\nThis closes a gap where a `disableClaudeAiConnectors` setting from the second source would have been ignored, so the connector-disable policy is now enforced more consistently.\n\n- Area: MCP\n- Names: `disableClaudeAiConnectors`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}