Repository navigation
copilot should notify the user of a disabled MCP server on startup #568
Description
Describe the bug
When invoking copilot using the --disable-mcp-server flag, it is unclear whether the indicated MCP server is actually disabled based on the start up messages. It would be helpful to indicate some way both configured and enabled MCP servers.
Affected version
0.0.355
Steps to reproduce the behavior
- Setup MCP server
- Invoke
copilot --disable-mcp-server <SERVER NAME>
Expected behavior
No response
Additional context
No response
Activity
patniko commentedon Oct 26, 2026
Thanks for the report. We've shipped fixes in this area since this was filed, and we believe this may now be resolved. Could you retest on the latest release (Copilot CLI v1.0.103) and let us know whether you still see it? If we don't hear back in a couple of weeks, we may close this issue — you can always reopen it.
Triaged as part of a Copilot SDK backlog review, with help from GitHub Copilot.