Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.304 ·

Organization-managed MCP server settings can now be held back

In some cases Claude Code now skips an organization's MCP server configuration file and loads only the default set of servers

Under the hood Internal Changes
JSON All of v2.1.304
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
MCPArea: what it touches
Internal ChangesKind: in v2.1.304,
Internal ChangesSection of the release

Unclear It is not clear what makes the organization's MCP configuration count as held, or when that happens.

What

MCP servers are outside programs that give Claude extra tools. An organization can manage which MCP servers its members use through a configuration file. When reading that organization configuration, Claude Code now has a new condition, described as the configuration being "held". When it applies, Claude Code skips the configuration file and uses its default set of servers, with no errors reported.

Why

This can change which organization-managed MCP servers load in a session.

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 doubtIt is not clear what makes the organization's MCP configuration count as held, or when that happens.

See this entry in the whole of v2.1.304 →

Feedback