Vscode in WSL using other environment to connect to MCP Servers

[lhemerly]

Does this issue occur when all extensions are disabled?: Yes

• VS Code Version: 1.99.0-insider
• OS Version: Windows_NT x64 10.0.26120 (Ubuntu WSL)

Steps to Reproduce:

1. Create a sample MCP server using python sdk and uv inside WSL
2. Add the MCP server command to the MCP server using uv. Ex:

"servers": {
    "My MCP Server": {
        "command": "uv",
        "args": [
            "run",
            "--with",
            "mcp[cli]",
            "mcp",
            "run",
            "path/to/your/mcp_server.py"
        ],
        "env": {}
    }
}

I also tried to create the bin with uv and point the server to it. Even though the command is available globally in the WSL terminal and the vscode integrated terminal I end up with the following error, both when using the direct command or using uv:

Error spawn uv ENOENT

Which indicates that the MCP server discovery is using another environment.

[elsewhat]

Experienced the same, but resolved it by moving the MCP servers to the workspace content (.vscode/mcp.json).

See #243687 (comment) for more info