-
Notifications
You must be signed in to change notification settings - Fork 31.1k
feat: add HTTP streamable option to MCP client #16406
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
feat: add HTTP streamable option to MCP client #16406
Conversation
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cubic reviewed 4 files and found no issues. Review PR in cubic.dev.
Hey @victorazesc, Thanks for the PR, We have created "GHC-2586" as the internal reference to get this reviewed. One of us will be in touch if there are any changes needed, in most cases this is normally within a couple of weeks but it depends on the current workload of the team. |
Thanks, happy to contribute! Let me know if I can help clarify anything during the review. |
Hey @victorazesc, Is this not the same as #15454? |
Actually, this PR doesn’t work — the client connection is being used incorrectly. |
I need this! 👍 |
I know, every body needs 😅 |
Summary
This PR introduces support for HTTP streamable responses when using the MCP client in the HTTP Request node.
This enables scenarios where the response body is large or long-lived (e.g., streamed AI completions).
How to test:
Added a new mcp client connector, added one http streamable source, like this image

Example workflow to test

Related Linear tickets, Github issues, and Community forum posts
No related tickets or issues at the moment.
Feature added proactively for advanced use cases with large or streamed data.
Review / Merge checklist
release/backport
(if the PR is an urgent fix that needs to be backported)