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
HomeReleasesv2.1.321entry #130

Claude Code v2.1.321 ·

MCP connections are checked against your organization's Claude in Chrome policy

Claude Code now checks MCP servers against the organization's Claude in Chrome policy before and after connecting, and skips refused ones

You'll notice Improvements
JSON All of v2.1.321
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.321,
ImprovementsSection of the release

Unclear Whether this check applies to every MCP server or only to the Claude in Chrome one is not clear.

What

MCP servers are outside programs that give Claude extra tools. Before connecting to one, Claude Code now checks it against your organization's policy for Claude in Chrome. This includes servers supplied by a program that runs Claude Code through the SDK, which used to connect without any such check.

  • If the policy refuses the server, Claude Code skips the connection and marks it as failed.
  • If the policy cannot be read, the server is also marked as failed, with a message saying Claude Code will try again.
  • After connecting and listing the server's tools, Claude Code checks it against the policy again.
Why

An organization's Claude in Chrome policy now blocks the Chrome MCP server more strictly. If a server fails to connect, a policy refusal or an unreadable policy may be 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 doubtWhether this check applies to every MCP server or only to the Claude in Chrome one is not clear.

See this entry in the whole of v2.1.321 →

Feedback