{"version":"2.1.221","anchor":"reconnecting-a-disabled-mcp-server-tells-you-to-enable-it","canonical_anchor":"reconnecting-a-disabled-mcp-server-tells-you-to-enable-it","heading":"Reconnecting a disabled MCP server tells you to enable it","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/reconnecting-a-disabled-mcp-server-tells-you-to-enable-it","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Reconnecting a disabled MCP server tells you to enable it\n\nReconnecting a disabled MCP server now just tells you to enable it first.\n\n**What**\n\nThe \/mcp reconnect flow checks the server's status first, and a disabled server reports that it needs enabling instead of running the reconnect state machine.\n\n**Details**\n\n- status check happens before any reconnect attempt, so no connection cycle is started for a disabled server\n- the message points you back at \/mcp to enable the server\n- other statuses still go through the normal reconnect path\n\n**Evidence**\n\n`enable it in \/mcp first`\n\n- Area: MCP\n- Names: `\/mcp`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}