Unactionable message when github-mcp-server is disable in Azure Dev Ops repository

[ellismg]

Describe the bug

We made changes to the CLI so that when you run it from inside a repository that is connected to an Azure DevOps remote we don't enable the built in GitHub MCP Server and instead print this message to the timeline:

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

However, if you run /mcp enable github-mcp-server, this doesn't actually work:

✗ Server "github-mcp-server" not found. Use /mcp to open the MCP server list.

Affected version

v0.0.411

Steps to reproduce the behavior

1. Start copilot in a repository with an AzDo remote so the above message triggers.
2. Run /mcp enable github-mcp-server

Expected behavior

The server should be enabled, instead of an error being printed.

Additional context

No response

[karolz-ms]

The /mcp enable github-mcp-server command works now, HOWEVER there is no good way to disable the killing of GH MCP server and it is extremely annoying when one has a setup with some GH and some AzDO remotes. And this is typical situation for many teams at MS (GH remote for public repository + AzDO remote for official, signed builds).

Would really love to have a way to disable killing GH MCP server, per-repository.

[ellismg]

I landed a change that will be in the next release to address this. Now, if you have a github remote, we'll keep the server enabled, regardless of if you have any azdo remotes.

If you just have azdo remotes, we'll keep the current behavior where we disable it, but with a message and you can use /mcp enable to get it back.