Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.221 ·

MCP reconnect and enable refuse to run against a disabled server

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

You'll notice Bug Fixes
JSON All of v2.1.221
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
MCPArea: what it touches
Bug FixesKind: in v2.1.221,
Bug FixesSection of the release
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.

Read from
Names in the bundle/mcp

See this entry in the whole of v2.1.221 →

Feedback