Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.248 Home All releases ←olderv2.1.247 v2.1.250newer→
Claude Code v2.1.248

MCP reconnect errors over the bridge report status, not server text

You'll notice
Useful2 Signal2
MCP

Bridge MCP reconnect failures show a status message; the server's own text goes to the log.

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 connected returns 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.

See this entry in the whole of v2.1.248 →