feat: Allow SSE transport to be initialized with a specific sessionId #286
Conversation
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
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.
Added the ability to initialize a SSEServerTransport with a specific sessionId, which enables stateless server handling and thus a horizontally scalable implementation.
Motivation and Context
It allows stateless servers, where a single MCP deployment can handle multiple servers statelessly.
How Has This Been Tested?
A specific test was added that validates that initializing the SSE transport with a specific ID works as expected.
Breaking Changes
None
Types of changes
Checklist
Additional context
None