{"version":"2.1.290","anchor":"claudeai-connector-list-tracking-mcp-allowlist-handles-cla","canonical_anchor":"claudeai-connector-list-tracking-mcp-allowlist-handles-cla","heading":"MCP allowlists now apply more strictly to claude.ai connectors","tier":"notice","area":"MCP","scope":"org","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/claudeai-connector-list-tracking-mcp-allowlist-handles-cla","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### MCP allowlists now apply more strictly to claude.ai connectors\n\nAn organisation's MCP allowlist now refuses claude.ai connectors it cannot find or does not admit, and matches them by their real name\n\n**Unclear.** What makes a connector count as admitted is not settled.\n\n**What**\n\nMCP servers are add-ons that give Claude extra tools, and claude.ai connectors are MCP servers you connect through your claude.ai account. An organisation can set an allowlist saying which servers are permitted.\n\nThe allowlist check has changed for claude.ai connectors:\n\n- A connector the check cannot find, or one that is not admitted, is now refused.\n\n- When matching by name, the check uses the connector's resolved name instead of only the key it has in the configuration.\n\nClaude Code also now keeps track of the connector list it fetched from claude.ai, including whether that list has settled or is unavailable. This handling sits on the path tied to the `ENABLE_CLAUDEAI_MCP_SERVERS` environment variable.\n\n**Why**\n\nAdministrators who restrict which MCP servers people can use get those rules enforced on claude.ai connectors too, instead of a connector getting through on a name that does not match.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: yes"}