{"version":"2.1.227","anchor":"mcp-explains-servers-changed-in-another-session","canonical_anchor":"mcp-explains-servers-changed-in-another-session","heading":"\/mcp explains servers changed in another session","tier":"use","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/mcp-explains-servers-changed-in-another-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### `\/mcp` explains servers changed in another session\n\n`\/mcp` now explains servers that another session enabled or disabled behind your back.\n\n**What**\n\n`\/mcp` now spells out cross-session cases that previously looked like bugs: a server re-enabled elsewhere so your disable did not stick, a server disabled elsewhere that needs a disable then re-enable in `\/mcp` to reconnect, a server disabled elsewhere that is not configured here, and a server still running in this session that will not come back after restart.\n\n**Evidence**\n\n`enable then disable each in \/mcp to make it stick`\n\n- Area: MCP\n- Names: `\/mcp`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}