{"version":"2.1.221","anchor":"inline-mcp-enable-disable-detects-changes-made-in-another-se","canonical_anchor":"inline-mcp-enable-disable-detects-changes-made-in-another-se","heading":"Inline \/mcp enable\/disable detects changes made in another session","tier":"use","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/inline-mcp-enable-disable-detects-changes-made-in-another-se","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Inline \/mcp enable\/disable detects changes made in another session\n\nWhen \/mcp enable or disable does nothing, it now tells you if another session already changed it.\n\n**What**\n\nWhen an inline `\/mcp enable` or `\/mcp disable` has nothing to do, it now tells you whether another session already changed that server's persisted state.\n\n**Details**\n\n- distinguishes a genuine no-op from a state another session flipped underneath you\n- explains whether the server keeps working in the current session and whether it reconnects on next launch\n- names the sequence of commands that makes the change stick\n\n**Evidence**\n\n`was re-enabled in another session, so this disable didn't persist`\n\n- Area: MCP\n- Names: `\/mcp enable`, `\/mcp disable`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 0\/5"}