Follow Discord
Sweep 30 Oct 2026 · 01:02Z Build v2.1.314 532 read Stable v2.1.308 Latest v2.1.314 Next v2.1.314 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.314entry #309

Claude Code v2.1.314 ·

MCP sign-in now records when a server rejects a token

MCP sign-in records 401 and 403 rejections with the token that was sent, and Clear authentication now checks a result field

Group of 3 Under the hood Internal Changes
JSON All of v2.1.314
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
MCPArea: what it touches
Internal ChangesKind: in v2.1.314,
Internal ChangesSection of the release

Unclear It is not shown how the recorded rejection is used, so the effect on when you are asked to log in again is unclear.

What

MCP servers are outside tools Claude Code connects to, and some need you to sign in. The sign-in handling now keeps track of when a server rejects access.

  • When an MCP server answers with a 401 or 403 (access refused), Claude Code now calls noteAuthRejection with the status and the authorization header it sent. This is stored per server address in a new _lastAuthRejection field.
  • The rejection is recorded before the existing check for a request with no authorization header, which still returns early. Before, such requests returned immediately and no rejection was noted.
  • The "Clear authentication" action now reads a .cleared value from the result of clearing stored sign-in data, instead of a plain yes/no answer. If clearing fails you still see "Authentication for ... was not cleared", now with the detail "sign-in data is still stored".

Why

Knowing which token a server rejected lets Claude Code tell whether a refusal applies to the sign-in it currently holds, which can affect when you are asked to sign in again.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not shown how the recorded rejection is used, so the effect on when you are asked to log in again is unclear.

See this entry in the whole of v2.1.314 →

Feedback