{"version":"2.1.299","anchor":"mcp-http-transport-notification-post-responses-discarded-r","canonical_anchor":"mcp-http-transport-notification-post-responses-discarded-r","heading":"MCP servers over HTTP no longer have redirects followed automatically","tier":"notice","area":"MCP","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/mcp-http-transport-notification-post-responses-discarded-r","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### MCP servers over HTTP no longer have redirects followed automatically\n\nClaude Code no longer follows redirects on authenticated MCP requests and now discards the reply body to notification messages\n\n**Unclear.** It is not clear whether an MCP server that answers with a redirect still connects, or now fails.\n\n**What**\n\nMCP 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:\n\n- 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\".\n\n- 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.\n\nBefore, reply bodies were passed through as they were and redirects were followed by default.\n\n**Why**\n\nNot 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.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}