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.221 Home All releases ←olderv2.1.220 v2.1.222newer→
Claude Code v2.1.221

/mcp enable and disable report per-server failures

Use it now
Useful3 Signal0
MCP

Enabling or disabling MCP servers now tells you when some didn't actually change.

/mcp
What

Bulk and single MCP server toggles no longer report success optimistically; servers that failed to change are counted and called out.

Details
  • Bulk enable/disable uses Promise.allSettled, logs each rejection, and appends a count of the ones that did not take.
  • The summary is assembled from "Enabled" or "Disabled", plus "MCP server(s)", plus, when some failed, " couldn't be changed — run /mcp to check)".
  • Single-server toggles surface a failure through the standard "Failed to " message.
  • Cross-session conflicts get their own assembled texts, for example "${e}" was re-enabled in another session, so this disable didn't persist.
Evidence

` couldn't be changed \u2014 run /mcp to check)`

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.221 →