{"version":"2.1.280","anchor":"mcp-wait-tool-now-reports-a-mcp-disabled-remedy","canonical_anchor":"mcp-wait-tool-now-reports-a-mcp-disabled-remedy","heading":"MCP wait tool now reports a 'mcp_disabled' remedy","tier":"notice","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/mcp-wait-tool-now-reports-a-mcp-disabled-remedy","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### MCP wait tool now reports a 'mcp_disabled' remedy\n\nWaiting for MCP servers now reports a specific 'mcp_disabled' remedy listing which servers are disabled\n\n**What**\n\nThe logic that waits for MCP servers to become ready (logged as `[WaitForMcpServers]`) now returns a `remedy` object with kind `mcp_disabled` and a list of the disabled servers, when applicable. This is in addition to its existing breakdown of ready, connected, failed, and disabled servers.\n\n**Why**\n\nThis gives a more actionable signal when MCP servers aren't ready because they're disabled, naming which servers are affected instead of just reporting a general readiness failure.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}