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

Claude Code v2.1.314 ·

Remote MCP sign-in tries a custom redirect address only after an extra check

When signing in to an MCP server over the remote bridge, Claude Code now tries a custom redirect address only if an extra check passes first

You'll notice Improvements
JSON All of v2.1.314
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
MCPArea: what it touches
ImprovementsKind: in v2.1.314,
ImprovementsSection of the release

Unclear It is not clear what the extra check tests, so it is unclear when the custom redirect address is now skipped.

What

MCP servers are outside tools that Claude Code can connect to, and some need you to sign in through OAuth, a standard way of granting access. Over the remote bridge, Claude Code used to try a custom redirect address whenever one was configured and no OAuth client ID was set. A redirect address is the place the sign-in page sends you back to. Now it tries that address only if an extra check passes first. When a connection fails, the step that handles sign-in also receives more detail about the sign-in in use.

Why

This affects how sign-in to MCP servers works over the remote bridge.

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 clear what the extra check tests, so it is unclear when the custom redirect address is now skipped.

See this entry in the whole of v2.1.314 →

Feedback