chore(js/mcp): Use StreamableHTTP transport for remote MCP.#3105
Merged
mbleigh merged 2 commits intolaunch/mcp-reduxfrom Jun 23, 2025
Merged
chore(js/mcp): Use StreamableHTTP transport for remote MCP.#3105mbleigh merged 2 commits intolaunch/mcp-reduxfrom
mbleigh merged 2 commits intolaunch/mcp-reduxfrom
Conversation
pavelgj
approved these changes
Jun 20, 2025
cabljac
pushed a commit
to invertase/genkit
that referenced
this pull request
Nov 25, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
StreamableHTTP is the correct default for a remote HTTP transport, defaulting to that going forward.
This also undoes my previous change to make all tools prefixed by hostname only. I think it makes more sense to prefix them by serverName otherwise why provide keys in servers?
So
fs/read_filenotmy-mcp-host/read_file.Checklist (if applicable):