{"version":"2.1.221","anchor":"mcp-reconnect-and-enable-refuse-to-run-against-a-disabled-se","canonical_anchor":"mcp-reconnect-and-enable-refuse-to-run-against-a-disabled-se","heading":"MCP reconnect and enable refuse to run against a disabled server","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/mcp-reconnect-and-enable-refuse-to-run-against-a-disabled-se","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### MCP reconnect and enable refuse to run against a disabled server\n\nReconnecting or enabling a disabled MCP server now fails with a message telling you to enable it in \/mcp.\n\n**What**\n\nReconnecting or enabling an MCP server that has been disabled now fails with a clear message instead of quietly bringing up a client you disabled.\n\n**Details**\n\n- 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.\n- Any client that connected in the meantime is closed.\n- Two user-facing texts are new in this build, both assembled around the server name: `\"${e}\" is disabled \u2014 enable it in \/mcp first` and `\"${e}\" was disabled in another session \u2014 disable and re-enable it in \/mcp, or restart, to reconnect`.\n\n**Evidence**\n\n`MCP server disabled; enable before reconnect`\n\n- Area: MCP\n- Names: `\/mcp`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}