Claude Code v2.1.221 ·
Inline /mcp enable/disable detects changes made in another session
When /mcp enable or disable does nothing, it now tells you if another session already changed it.
Use it nowTier: how much it should matter to you
4Useful: 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
When an inline /mcp enable or /mcp disable has nothing to do, it now tells you whether another session already changed that server's persisted state.
Details
- distinguishes a genuine no-op from a state another session flipped underneath you
- explains whether the server keeps working in the current session and whether it reconnects on next launch
- names the sequence of commands that makes the change stick
Evidence
was re-enabled in another session, so this disable didn't persist
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundle/mcp enable/mcp disable
See this entry in the whole of v2.1.221 →
