Skip to content
Discussion options

You must be logged in to vote

"Reconnection enabled" does not help here because the supervisor only reacts to a connection that drops, and a 404 is not a drop.

packages/mcp/mcp-client/src/connection.ts:1-13 states the contract: it owns the client/transport generations, keeps the tool registry in sync with the live generation, and — "when the connection drops — restarts the configured server with bounded exponential backoff". The trigger is the transport generation ending. An HTTP 404 from a Streamable HTTP endpoint is a completed response carrying an error body; the transport stays up, the generation never ends, so no restart is scheduled and the next call reuses the same session id. That is exactly the "keeps using t…

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Answer selected by xzdbadboy
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants