{"version":"2.1.251","anchor":"cloud-routines-explain-in-more-detail-why-a-connector-is-mis","canonical_anchor":"cloud-routines-explain-in-more-detail-why-a-connector-is-mis","heading":"Cloud routines explain in more detail why a connector is missing","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/cloud-routines-explain-in-more-detail-why-a-connector-is-mis","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Cloud routines explain in more detail why a connector is missing\n\nWhen a cloud routine can't load a connector, you now see the specific reason.\n\n**What**\n\nThe 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.\n\n**Details**\n\n- Reasons covered separately: organization lockdown, a restricted account, opting out via `disableClaudeAiConnectors` or `ENABLE_CLAUDEAI_MCP_SERVERS`, safe mode, and a missing OAuth scope.\n- Duplicate connector display names are deduplicated, and connectors suppressed because they duplicate a manually configured MCP server are called out as such.\n\n**Evidence**\n\n`Loading of claude.ai connectors is disabled in this Claude Code session by the organization's managed MCP configuration`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}