Fix MCP server connectivity check using 0.0.0.0 addresses#10092
Closed
Fix MCP server connectivity check using 0.0.0.0 addresses#10092
Conversation
Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com>
Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Debug auto-assign issue workflow failure
Fix MCP server connectivity check using 0.0.0.0 addresses
Jan 15, 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
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.
The Auto-Assign Issue workflow failed because
check_mcp_servers.shwas extracting server URLs directly from the gateway config, which contains0.0.0.0bind addresses. Connecting to0.0.0.0as a client fails.Changes
${GATEWAY_URL}/mcp/${SERVER_NAME}pattern instead of extracting.urlfrom configtype == "http"or URL field exists before attempting connectionAuthorizationheaders from config as beforeBefore:
After:
The script already receives the correct gateway URL as its second parameter (
http://localhost:8080) but wasn't using it.Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.