mcp: make the streamable client transport less strict #524
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
In practice, the streamable client transport was having trouble connecting to various backends, because they are nonconformant in various ways. While it would be nice if all servers conformed to the spec, in practice there are certain spec violations that are recoverable, and we can and should recover them. Specifically: - tolerate 404 instead of 405 for the hanging GET (modelcontextprotocol#393) - tolerate (=ignore) spurious response body for notifications and responses, since we know none are expected Additionally: - fix a bug that we weren't parsing Content-Type correctly. - update examples/client/listfeatures to accept a streamable endpoint Fixes modelcontextprotocol#521
findleyr
force-pushed
the
streamableclient
branch
from
de9ca2c to
5aab47f
Compare
jba
approved these changes
Sep 24, 2025
samthanawalla
approved these changes
Sep 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
In practice, the streamable client transport was having trouble connecting to various backends, because they are nonconformant in various ways.
While it would be nice if all servers conformed to the spec, in practice there are certain spec violations that are recoverable, and we can and should recover them. Specifically:
failed to reconnect: Not Foundafter initalize in stateless HTTPPOSTserver #393)Additionally, fix a bug that we weren't parsing Content-Type correctly.
Fixes #521