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 ·

Programs driving Claude Code can now deny tools and reconnect servers awaiting sign-in

Updating MCP servers from a program can now include tools to deny, and servers waiting for sign-in are retried afterwards

Use it now No documentation found New Features
JSON All of v2.1.321
Use it nowTier: how much it should matter to you
4Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SDKArea: what it touches
New FeaturesKind: in v2.1.321,
What probably matters to youSection of the release

Unclear The retry of servers waiting for sign-in sits behind a check whose setting is not known, so it may not run for every session.

What

MCP servers are add-ons that give Claude extra tools. A program that drives Claude Code through the SDK (the developer kit for controlling Claude Code from code) or from a remote host can replace the list of MCP servers with a single mcp_set_servers request. That request changed in these ways:

  • deniedTools: a new option listing tools Claude may not use. These denials are added to the permission rules for the session.
  • Servers waiting for sign-in: after the list is replaced, any server the request names that is in the "needs authentication" state is tried again. If it still cannot connect, Claude Code logs "Could not connect after mcp_set_servers".
  • SDK server settings: these can now carry a list of tools tied to automatic permission decisions.
  • Always-deny rules: certain held-back artifact entries are now checked against your always-deny rules before they are used.
Why

A host program can block tools and get stalled servers connected again without restarting Claude Code.

Read from
Names in the bundlemcp_set_servers
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 doubtThe retry of servers waiting for sign-in sits behind a check whose setting is not known, so it may not run for every session.

See this entry in the whole of v2.1.321 →

Feedback