You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
MCPArea: what it touches
ImprovementsKind: in v2.1.222,
What probably matters to youSection of the release
What
A 401 from the claude.ai proxy that a token refresh cannot fix now becomes a typed error telling you to run /login, instead of silently returning the original failed response.
Details
error code CLAUDEAI_BEARER_REJECTED, recognised by connect, tools/list, prompts/get and skills/list
sets discoveryBearerRejected on the client and skips the usual "degraded" telemetry
emits mcp_connect_claudeai_bearer_rejected and mcp_reconnect_bearer_rejected
the failed entry is evicted from the connection cache so a later attempt retries
Evidence
claude.ai rejected the session token — it may lack connector scopes or be invalid. Run /login.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeFixed claude.ai connectors being falsely marked as needing authorization when the session token is invalid — they now show a /login hint…
