{"version":"2.1.321","anchor":"plugin-mcp-oauth-refuses-sign-in-if-the-connector-check-fail","canonical_anchor":"plugin-mcp-oauth-refuses-sign-in-if-the-connector-check-fail","heading":"Plugin MCP sign-in stops if your organization's connector settings cannot be checked","tier":"notice","area":"MCP","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/plugin-mcp-oauth-refuses-sign-in-if-the-connector-check-fail","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Plugin MCP sign-in stops if your organization's connector settings cannot be checked\n\nA plugin's MCP server sign-in is stopped when Claude Code cannot check it against your organization's connector settings\n\n**What**\n\nPlugins can bring their own MCP servers, outside services that give Claude Code extra tools. When such a server needs you to sign in, Claude Code may first check it against your organization's connector settings, the rules your organization sets for which outside services are allowed. If that check cannot be completed, Claude Code now stops the sign-in. It shows: \"Could not check this MCP server against your organization's connector settings, so the sign-in was stopped.\"\n\n**Why**\n\nWhen the check fails, Claude Code refuses rather than letting the sign-in through, so a plugin's server cannot slip past your organization's rules.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: yes"}