Server implementation of Streamable HTTP #461
Open
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
RamAnanth
changed the title
2 tasks
|
any update? waiting to use. |
|
If we're looking for a client implementation to test against, this is the PR for the inspector to support Streamable HTTP. It's getting close. |
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.
Motivation and Context
This PR implements the Streamable HTTP transport for the MCP protocol (revision 2025-03-26) and addresses the server and tests portion mentioned in #443
How Has This Been Tested?
All existing unit tests are passing. Added a comprehensive unit test to verify different features of the Streamable HTTP Transport requirements.
Breaking Changes
None
Types of changes
Checklist