Claude Code v2.1.221 ·
/mcp enable and disable report per-server failures
Enabling or disabling MCP servers now tells you when some didn't actually change.
Use it nowTier: how much it should matter to you
3Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
MCPArea: what it touches
ImprovementsKind: in v2.1.221,
What probably matters to youSection of the release
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.
See this entry in the whole of v2.1.221 →
