feat: added optional parameter to specify which host interface to listen on when using http transport#419
Open
feat: added optional parameter to specify which host interface to listen on when using http transport#419
Conversation
added 3 commits
March 16, 2026 20:33
…default host of "localhost" causes problems on some systems when connecting from a Docker container if not bound to 0.0.0.0. Specifying the specific host option allows this behavior, while still utilizing the default localhost as a fallback. Updated docs, and passes all tests that expect the default to be localhost. Currently tests don't try an alternative host.
… server on 127.0.0.1 and 0.0.0.0
…sing the declared option types, causing the npm run build to fail. Also found missing host parameter not realized until running it.
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
1 participant
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.
Treatment of the hard-coded "localhost" interface can vary by machine environment. This causes a problem specifically when trying to connect from a Docker service (ex: Open-WebUI via MCP) to QMD using host.docker.internal to localhost - it fails to connect. Specifying the 0.0.0.0 interface allows the connection, but alternatives should also be possible.
The --host parameter is optional, and defaults to the original behavior. Documentation and tests were added to support the change, while preserving the style. All tests pass.