When a cloud routine can't load a connector, you now see the specific reason.
What's wrong with this entry?
The text telling Claude which MCP connectors a cloud routine can use now names the specific reason a connector was not loaded, instead of leaving it unexplained.
- Reasons covered separately: organization lockdown, a restricted account, opting out via
disableClaudeAiConnectorsorENABLE_CLAUDEAI_MCP_SERVERS, safe mode, and a missing OAuth scope. - Duplicate connector display names are deduplicated, and connectors suppressed because they duplicate a manually configured MCP server are called out as such.
Loading of claude.ai connectors is disabled in this Claude Code session by the organization's managed MCP configuration
Strings lifted out of the shipped bundle, so the claim above can be checked against them.