What
Reconnecting an MCP server through the bridge now routes failures through a shared helper. A failed server's own error text is written to the error log rather than raised, and what you see is a status-based message instead.
Details
- A client already reporting
connectedreturns without doing anything; any other status throws a message naming that status. - The bridge's MCP handlers moved from generic errors to a dedicated error class that carries a separate telemetry message, covering server-not-found, disabled in another session, blocked by managed policy, unsupported transport, and OAuth callback failure.
Evidence
MCP server disabled in another session; auth refused
Strings lifted out of the shipped bundle, so the claim above can be checked against them.