In a repo with GitHub and AzDo upstreams, the GitHub mcp is disabled, and seemingly can't be re-enabled

[davidwengier]

Describe the bug

I'm in a working folder that has https://github.com/dotnet/razor cloned, that has my fork as a remote (origin), the dotnet org repo as a remote (upstream) and our Azure DevOps mirror as another upstream (azdo). When I start copilot, I get told:

● Detected Azure DevOps repository. GitHub MCP server has been disabled. Use /mcp enable github-mcp-server to re-enable.

This is annoying, as there is clearly both repos connected, and in fact GitHub outnumbers AzDo 2 to 1 (though I don't think that should matter). Whats more annoying though, is running the command suggested gives me:

✗ Server "github-mcp-server" not found. Use /mcp show to list available servers.

Obviously this is correct, as I have not configured a github mcp server, since it's inbuilt. /mcp show does not list the built-in server.

Affected version

GitHub Copilot CLI 0.0.409

Steps to reproduce the behavior

1. Clone a repo from GitHub
2. Add a remote from AzDo
3. Run copilot

Expected behavior

Ideally, the GitHub MCP isn't disabled. More ideally, the command re-enable it works.

Additional context

No response