{"version":"2.1.283","anchor":"an-http-404-from-an-mcp-server-with-no-session-is-no-longer","canonical_anchor":"an-http-404-from-an-mcp-server-with-no-session-is-no-longer","heading":"A \"not found\" reply from a sessionless HTTP MCP server no longer forces a reconnect","tier":"notice","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/an-http-404-from-an-mcp-server-with-no-session-is-no-longer","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### A \"not found\" reply from a sessionless HTTP MCP server no longer forces a reconnect\n\nAn HTTP MCP server that returns 404 during a tool call without a session is now treated as a normal error, not an expired session\n\n**What**\n\nAn MCP server is an add-on that gives Claude Code extra tools, and some are reached over HTTP. Claude Code has long treated an HTTP 404 (\"not found\") reply during a tool call as a sign that the server's session had expired, and it would drop its cached connection and reconnect.\n\nThat now only happens when the connection actually had a session ID. If an HTTP MCP server was used without a session and returns 404 during a tool call, Claude Code handles it as an ordinary error from that tool.\n\n**Why**\n\nServers that keep no session and answer 404 simply because something they were asked for does not exist no longer trigger pointless reconnects.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}