{"version":"2.1.319","anchor":"plugin-mcp-servers-can-be-blocked-by-connector-policy","canonical_anchor":"plugin-mcp-servers-can-be-blocked-by-connector-policy","heading":"Plugin MCP servers blocked by your organization's connector settings are removed and explained","tier":"notice","area":"MCP","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/plugin-mcp-servers-can-be-blocked-by-connector-policy","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Plugin MCP servers blocked by your organization's connector settings are removed and explained\n\nPlugin-provided MCP servers that your organization's connector settings block are removed, with a message saying an admin can change it\n\n**What**\n\nAn MCP server is an add-on that gives Claude extra tools, and plugins can bring their own. An organization can block some connectors in its settings. Now:\n\n- Plugin MCP servers that the organization's connector settings block are removed while Claude Code sorts out duplicate servers. A log line says how many plugin servers were removed.\n\n- Each blocked server gets a status entry, `mcp-server-connector-blocked`, naming the plugin and the server.\n\n- The message says the server \"is turned off by your organization's connector settings\". It adds that an admin can change this and that a new session is needed afterwards.\n\n**Why**\n\nIf a plugin's server goes missing, you can see that your organization's policy turned it off. You also know that changing it needs an admin and a fresh session.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: yes"}