Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.265 ·

Legacy HTTP+SSE MCP transport gets a guarded OAuth-avoidance dial path

Older MCP servers using the legacy HTTP+SSE protocol no longer get wrongly prompted into an OAuth login flow

TierYou'll noticehow much it should matter to you
Useful2my rating, 1 to 5
Signal1worth watching, 1 to 5
AreaMCPwhat it touches
KindBug Fixesin v2.1.265,
You'll notice

Older MCP servers using the legacy HTTP+SSE protocol no longer get wrongly prompted into an OAuth login flow

What

For MCP servers (external tools Claude Code connects to) that use the older HTTP+SSE connection method rather than newer transports, Claude Code now checks whether a 401 "unauthorized" response on the connection request really means the server wants OAuth login. If the server's earlier setup request didn't return a 405 "method not allowed" response, the 401 is treated as a genuine OAuth prompt. If it did return 405, Claude Code now refuses to start an OAuth flow at all.

Why

This avoids incorrectly launching an OAuth sign-in flow against MCP servers that don't actually require one, which previously could have interrupted the user with an unnecessary login prompt.

See this entry in the whole of v2.1.265 →

Feedback