{"version":"2.1.221","anchor":"mcp-enable-and-disable-report-per-server-failures","canonical_anchor":"mcp-enable-and-disable-report-per-server-failures","heading":"\/mcp enable and disable report per-server failures","tier":"use","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/mcp-enable-and-disable-report-per-server-failures","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### \/mcp enable and disable report per-server failures\n\nEnabling or disabling MCP servers now tells you when some didn't actually change.\n\n**What**\n\nBulk and single MCP server toggles no longer report success optimistically; servers that failed to change are counted and called out.\n\n**Details**\n\n- Bulk enable\/disable uses `Promise.allSettled`, logs each rejection, and appends a count of the ones that did not take.\n- The summary is assembled from \"Enabled\" or \"Disabled\", plus \"MCP server(s)\", plus, when some failed, \" couldn't be changed \u2014 run \/mcp to check)\".\n- Single-server toggles surface a failure through the standard \"Failed to \" message.\n- Cross-session conflicts get their own assembled texts, for example `\"${e}\" was re-enabled in another session, so this disable didn't persist`.\n\n**Evidence**\n\n`` couldn't be changed \\u2014 run \/mcp to check)``\n\n- Area: MCP\n- Names: `\/mcp`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 0\/5"}