feat: define two endpoints for SSE to match MCP Spec #32
+188
−18
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
Collaborator
|
Thanks for the PR @psekar , I'll take a look at this and get back to you. Is looking good on the documentation front, just need to look a bit closer to the tests |
ChrisJBurns
reviewed
Aug 12, 2025
ChrisJBurns
reviewed
Aug 20, 2025
ChrisJBurns
approved these changes
Aug 23, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 MCP spec mandates the use of two separate endpoints
one for SSE stream (i.e. server-to-client communication)
one for commands (i.e. client-to-server communication)
Although, the Http + SSE is deprecated in favor of StreamableHttp, dual endpoint to added for backward compatibility and older implementations.
Fixes #26