{"version":"2.1.248","anchor":"mcp-reconnect-errors-over-the-bridge-report-status-not-serve","canonical_anchor":"mcp-reconnect-errors-over-the-bridge-report-status-not-serve","heading":"MCP reconnect errors over the bridge report status, not server text","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/mcp-reconnect-errors-over-the-bridge-report-status-not-serve","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### MCP reconnect errors over the bridge report status, not server text\n\nBridge MCP reconnect failures show a status message; the server's own text goes to the log.\n\n**What**\n\nReconnecting 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.\n\n**Details**\n\n- A client already reporting `connected` returns without doing anything; any other status throws a message naming that status.\n- 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.\n\n**Evidence**\n\n`MCP server disabled in another session; auth refused`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}