Describe the feature or problem you'd like to solve
I have MCP servers recognized by VSCode. I shouldn't need to re-add them to Github Copilot CLI.
Proposed solution
Eventually and on windows, both (and full VS for that matter) should use the windows-wide MCP registry. Until that happens and for other platforms, they should try to share / look into each others configs to recognize MCP servers and somehow merge.
If I configure servers in VSCode (where its copilot sees it) they should be usable from VS (not what this ticket is about, I know) and Copilot CLI (what this ticket is about).
Ideally, this config recognition & merge should work across WSL boundary.
Example prompts or workflows
N/A
Additional context
Windows, not WSL.
Describe the feature or problem you'd like to solve
I have MCP servers recognized by VSCode. I shouldn't need to re-add them to Github Copilot CLI.
Proposed solution
Eventually and on windows, both (and full VS for that matter) should use the windows-wide MCP registry. Until that happens and for other platforms, they should try to share / look into each others configs to recognize MCP servers and somehow merge.
If I configure servers in VSCode (where its copilot sees it) they should be usable from VS (not what this ticket is about, I know) and Copilot CLI (what this ticket is about).
Ideally, this config recognition & merge should work across WSL boundary.
Example prompts or workflows
N/A
Additional context
Windows, not WSL.