Changing an MCP endpoint is not just a deployment detail. The endpoint URL is part of the deployed client contract. A server can ship a working new endpoint while older clients still become unavailable because their local configuration continues calling the old path.
Why this breaks silently
Installed MCP clients do not discover server migrations automatically. They read whatever is in their project, global, or packaged configuration. If the old URL returns an HTML 404, the failure can appear as:
server unavailable;
tools/list timeout;
version discovery failure;
a healthy network connection followed by an invalid protocol response.
Separate package updates from installed updates
A repository fix only helps future installs.…