{"version":"2.1.227","anchor":"bulk-mcp-reconnect-and-enable-disable-report-changes-made-in","canonical_anchor":"bulk-mcp-reconnect-and-enable-disable-report-changes-made-in","heading":"Bulk MCP reconnect and enable\/disable report changes made in other sessions","tier":"use","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/bulk-mcp-reconnect-and-enable-disable-report-changes-made-in","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Bulk MCP reconnect and enable\/disable report changes made in other sessions\n\nBulk MCP reconnect and enable now summarise when another session changed servers behind you.\n\n**What**\n\n`\/mcp reconnect all` and the enable\/disable flows now add a single summary note when servers were changed from another running session, for example that N servers were re-enabled elsewhere so your disable did not stick. Previously only per-server versions of these sentences existed.\n\n**Details**\n\n- The note tells you to disable and re-enable in `\/mcp`, or restart, to reconnect affected servers.\n\n**Evidence**\n\n`MCP server(s) were disabled in another session \\u2014 disable and re-enable them in \/mcp, or restart, to reconnect.`\n\n- Area: MCP\n- Names: `\/mcp reconnect all`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}