Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.308 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.299entry #98

Claude Code v2.1.299 ·

MCP servers over HTTP no longer have redirects followed automatically

Claude Code no longer follows redirects on authenticated MCP requests and now discards the reply body to notification messages

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

Unclear It is not clear whether an MCP server that answers with a redirect still connects, or now fails.

What

MCP servers are outside programs that give Claude extra tools, and some are reached over the web (HTTP). Two things change in how Claude Code talks to them:

  • Redirects are no longer followed automatically for requests that carry login details. A redirect is when a server answers "go to this other address instead".
  • When a server answers a notification (a one-way message that expects no answer) with an accepted or success reply, Claude Code throws the reply body away and treats it as empty.

Before, reply bodies were passed through as they were and redirects were followed by default.

Why

Not following redirects stops your login details being sent on to a different address. Discarding notification replies avoids Claude Code waiting on a reply body it does not need.

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 whether an MCP server that answers with a redirect still connects, or now fails.

See this entry in the whole of v2.1.299 →

Feedback