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 reconnect and enable refuse to run against a disabled server

You'll notice
Useful3 Signal0
MCP

Reconnecting or enabling a disabled MCP server now fails with a message telling you to enable it in /mcp.

/mcp
What

Reconnecting or enabling an MCP server that has been disabled now fails with a clear message instead of quietly bringing up a client you disabled.

Details
  • The MCP client store checks the disabled set before reconnecting or enabling, throwing errors tagged "MCP server disabled; enable before reconnect", "MCP server disabled during reconnect" and the equivalent for the enabling path.
  • Any client that connected in the meantime is closed.
  • Two user-facing texts are new in this build, both assembled around the server name: "${e}" is disabled — enable it in /mcp first and "${e}" was disabled in another session — disable and re-enable it in /mcp, or restart, to reconnect.
Evidence

MCP server disabled; enable before reconnect

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 →