Follow Discord
Sweep 08 Oct 2026 · 18:53Z Build v2.1.295 516 read Stable v2.1.286 Latest v2.1.295 Next v2.1.295 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.290entry #177

Claude Code v2.1.290 ·

MCP allowlists now apply more strictly to claude.ai connectors

An organisation's MCP allowlist now refuses claude.ai connectors it cannot find or does not admit, and matches them by their real name

You'll notice Improvements
JSON All of v2.1.290
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
MCPArea: what it touches
ImprovementsKind: in v2.1.290,
ImprovementsSection of the release

Unclear What makes a connector count as admitted is not settled.

What

MCP 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.

The allowlist check has changed for claude.ai connectors:

  • A connector the check cannot find, or one that is not admitted, is now refused.
  • When matching by name, the check uses the connector's resolved name instead of only the key it has in the configuration.

Claude 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.

Why

Administrators 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.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat makes a connector count as admitted is not settled.

See this entry in the whole of v2.1.290 →

Feedback