/mcp now explains servers that another session enabled or disabled behind your back.
What's wrong with this entry?
/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.
enable then disable each in /mcp to make it stick
Strings lifted out of the shipped bundle, so the claim above can be checked against them.