feat(mcp): expose running HTTP listeners through status - #1732
Open
mariusvniekerk wants to merge 1 commit into
Open
feat(mcp): expose running HTTP listeners through status#1732mariusvniekerk wants to merge 1 commit into
mariusvniekerk wants to merge 1 commit into
Conversation
MCP clients need the actual listening port and backend target to connect to an existing HTTP server. Fixed port guesses do not work when several servers run or when a listener binds port zero. Publish local listener records after binding and expose them through mcp status. Keep bearer values in private files so status output can locate credentials without printing them.
roborev: Combined Review (
|
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.
agentsview mcp status --jsonreports running HTTP MCP listeners, including their actual bound ports, backend targets, and private token-file paths. Clients can discover an existing listener instead of guessing its port. Status does not start a daemon or print bearer tokens.Listeners publish after binding and remove their records on orderly shutdown. Status omits dead processes; stdio sessions do not appear in the list.