Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.321 ·

Organizations can block MCP server connections that send certain headers

Claude Code skips connecting to an MCP server when the headers it would send fall under an organization's connector block

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

Unclear Where the organization's connector block is set, and which users it applies to, is not stated.

What

MCP servers are add-on programs that give Claude extra tools. Some are reached over the network. Before connecting to one of these, Claude Code now checks the headers it is about to send against a block set by your organization's managed policy. Headers are extra pieces of information sent with each request.

If the headers match the block, Claude Code does not connect. The server shows as failed with a managed-policy reason, and the log says the connection was skipped because the headers are under the organization's connector block.

Why

Organizations can now stop specific MCP servers from connecting based on their headers. If a server you use suddenly fails with a managed-policy reason, this block is the cause.

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 doubtWhere the organization's connector block is set, and which users it applies to, is not stated.

See this entry in the whole of v2.1.321 →

Feedback