MCP enable/disable failures report the underlying error

Turning an MCP server on or off now shows the real error instead of a vague message.

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

ImprovementsKind: in v2.1.221, 03 Aug 26

ImprovementsSection of the release

What

Failing to toggle an MCP server now shows the actual error instead of a generic "it may have been removed" message.

Details

Applies to both the /mcp slash-command path and the plugin/MCP toggle UI.
Toggling a server from the manager surfaces the error inline rather than discarding it.
The failure text is assembled at runtime from the action, the server name and the error.

Evidence

Failed to

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from

Names in the bundle/mcp

The build it came inv2.1.221

3 Aug 2026 · 308 entries, this one is #108.

Either side of it

Open the release →

Names in this entry

slash/mcp
Manage MCP server connections and OAuth authentication. Run with no argument to open the interactive list, pass reconnect <server> to reconnect one disconnected server, or pass enable/disable with a server name or all to change connection state without opening the dialog. Also available in non-interactive mode (-p), where running it with no argument prints a text summary of server status instead of opening the list; requires Claude Code v2.1.205 or later

Is this right?