[Bug] Copilot reports failure when extension-point contributed MCP server has changed

[martinlippert]

I have a plugin that contributes an MCP server via the extension point. That works fine in general.

But when the configuration for this MCP server changes, the Copilot plugin always complains about that there is a failure to connect to the MCP server. It seems to me like the Copilot plugin keeps an internal config for those MCP servers from extensions and uses this internal cached config to connect to it, before it checks for changes in the configuration.

There are two scenarios to take into account here:

• What happens when the extension doesn't return a config for a specific MCP server anymore? (I guess the MCP server is identified by the ID from the extension? Or the name from the config that the extension provides dynamically)

• What happens when the extension continues to deliver a configuration for the MCP server, but this configuration has changed (the http MCP server is now in a different port)

In both cases, the failure shows up (again, because Copilot seems to use the old config first) before the changes are taken into account.