Under the hood
Whether claude.ai connectors are disabled is now checked against a second settings source too
What
The 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.
Why
This 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.
Names in the bundledisableClaudeAiConnectors
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up disableClaudeAiConnectors, on Deploy managed settings.
* `deniedMcpServers` and [`disableClaudeAiConnectors`](/docs/en/settings-reference#disableclaudeaiconnectors): an entry or a `true` in any admin source applies. Requires Claude Code v2.1.273 or latermanaged-settings see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up disableClaudeAiConnectors, on Deploy managed settings.
Anthropic's release notes agree
Fixed allowManagedMcpServersOnly, deniedMcpServers and disableClaudeAiConnectors set via MDM or managed-settings.json being ignored when…