Run MCP Streamable HTTP server in stateless mode#86
Merged
Conversation
The server used rmcp's default stateful_mode, keeping every session in LocalSessionManager's RAM. Any restart of the binary (or its tunnel) invalidated existing session IDs; clients that did not renegotiate initialize — observed with Gemini CLI — kept reusing the stale ID and received 404 Not Found indefinitely. Froid only exposes request/response tools, resources, and prompts and does not rely on server-initiated SSE streams, so stateless mode covers the full surface while making each request self-contained and immune to session loss across restarts. The integration test is aligned to the new configuration to keep coverage representative of production.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The server used rmcp's default stateful_mode, keeping every session in LocalSessionManager's RAM. Any restart of the binary (or its tunnel) invalidated existing session IDs; clients that did not renegotiate initialize — observed with Gemini CLI — kept reusing the stale ID and received 404 Not Found indefinitely.
Froid only exposes request/response tools, resources, and prompts and does not rely on server-initiated SSE streams, so stateless mode covers the full surface while making each request self-contained and immune to session loss across restarts.
The integration test is aligned to the new configuration to keep coverage representative of production.