Repository navigation
Remove port-finding logic for MCP server's HTTP transport - #257
Merged
Merged
Conversation
AdrianLC
approved these changes
Oct 7, 2026
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.
When the requested port was busy,
tiger mcp start httpsilently fell back to the next free port. MCP clients are configured to connect on a specific port, so a server listening somewhere else just leaves them unable to connect. I really can't think of many situations where a user would want a server to start on a different port than the one they specified.This PR updates the logic so the server listens only on the given port and fails with the underlying listen error if it's already in use. This is simpler and less surprising behavior.