Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.227 Home All releases ←olderv2.1.226 v2.1.228newer→
Claude Code v2.1.227

Bulk MCP reconnect and enable/disable report changes made in other sessions

Use it now
Useful3 Signal2
MCP not in their notes

Bulk MCP reconnect and enable now summarise when another session changed servers behind you.

/mcp reconnect all
What

/mcp reconnect all and the enable/disable flows now add a single summary note when servers were changed from another running session, for example that N servers were re-enabled elsewhere so your disable did not stick. Previously only per-server versions of these sentences existed.

Details
  • The note tells you to disable and re-enable in /mcp, or restart, to reconnect affected servers.
Evidence

MCP server(s) were disabled in another session \u2014 disable and re-enable them in /mcp, or restart, to reconnect.

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.227 →