What probably matters to youSection of the release
What
A connected MCP server whose discovery bearer token was rejected now says so in the server list and in the reconnect result, rather than the state being tracked only internally.
Details
Message directs you to run /login and then reconnect.
A successful tools/list now clears discoveryAuthFailure in both MCP client implementations, so a recovered server stops showing the warning.
Evidence
but your claude.ai session token was rejected. Run /login, then reconnect.
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…
