Streamable HTTP client transport #416
Draft
+193
−1
Conversation
This file contains 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
josh-newman
changed the title
|
Are you also including authorisation the spec says oauth 2 |
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.
Client implementation of spec version 2025-03-26's new transport.
Motivation and Context
The 2025-03-26 spec introduces a new HTTP transport mechanism (with fallback to the previous one). I didn't see a reference implementation available yet so we've made this experimental one.
How Has This Been Tested?
We've tested with local and remote MCP servers in our product (Lutra).
Breaking Changes
None.
Types of changes
Checklist
Additional context
This is a draft. I'm not sure how the maintainers would like to handle updating
LATEST_PROTOCOL_VERSIONandSUPPORTED_PROTOCOL_VERSIONS. And I don't have automated tests for the new transport.