Incorrectly Configured MCP Servers Do Not Log Anything

[Cobular]

Describe the bug

When an MCP server is setup with the wrong transport applied, it will never log anything about that failure, and the only indication of an issue will be the model failing to see the server. The server appears as enabled and there is no logging emitted at the default log level.

Affected version

0.0.330 Commit: a8bfefe

Steps to reproduce the behavior

1. Start copilot with no arguments
2. Add an MCP server, but use the wrong transport (i.e. SSE instead of HTTP)
3. Save the server
4. Ask the model what MCP servers it sees

The model will not see the newly added mcp, but there will be no other indication that adding the server did not work.

Expected behavior

There should be some indication of the failure even without elevated logging. Maybe as part of the server setup flow?

Additional context

No response

[examon]

As of v0.0.410, misconfigured MCP servers surface connection errors in the session timeline at the default log level, and /mcp show displays a failure indicator for servers that couldn't connect. A warning message also directs you to /mcp show <server-name> for details. If you're still seeing silent failures on a current version, feel free to reopen this issue.