`copilot` should notify the user of a disabled MCP server on startup
Open
area:mcp
- Dominant language
- Shell
- Stars
- 11.2k
- Forks
- 1.9k
- Avg merge
- 14h 16m
- Merged PRs (30d)
- 6
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
1. Setup MCP server
2. Invoke `copilot --disable-mcp-server `
### Expected behavior
_No response_
### Additional context
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.