Client streamable http #48
Merged
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.
What changed?
Implemented complete streamable HTTP client transport from scratch following the MCP specification, plus added consistent
close()method to both client and server transport interfaces.Why?
We needed a robust HTTP transport implementation to enable client sessions to connect to HTTP-based MCP servers. The existing draft was incomplete and didn't handle the complex streaming scenarios required by the spec.
Impact
ClientStreamManagerabstraction with proper background task cleanupclose()methods for explicit resource cleanupTesting
Review notes
ClientStreamManagerabstraction cleanly handles multiple SSE streams per serverChecklist