Test: Workspace-root MCP configuration entry points #338161

Refs: #335551

• anyOS Ulugbek Abdullaev (@ulugbekna)

Complexity: 2

Authors: Vritant Bhardwaj (@vritant24)

Create Issue

Verification steps

1. Open a disposable folder that does not contain .mcp.json or .vscode/mcp.json.

2. Run MCP: Add Server and add a Command (stdio) server:

   npx -y @modelcontextprotocol/server-everything
   

3. Choose Workspace (folder-name) as the destination.

4. Verify:

   • A .mcp.json file is created at the workspace root.
   • The server is written under mcpServers.
   • No .vscode/mcp.json file is created.

5. Run MCP: Open Workspace Folder MCP Configuration.

6. Verify the root .mcp.json opens directly without a file picker.

Root and legacy files together

1. Create .vscode/mcp.json in the same folder with a different server.
2. Run MCP: Add Server again and choose Workspace (folder-name).
3. Verify you can choose between the root .mcp.json and legacy .vscode/mcp.json.
4. Choose one file and complete the addition.
5. Verify the new server is added only to the selected file and the other file remains unchanged.
6. Run MCP: Open Workspace Folder MCP Configuration.
7. Verify a picker offers both files and opens the selected file.

Expected: New workspace MCP servers can be added to the workspace-root .mcp.json without replacing existing .vscode/mcp.json configuration. When only one configuration exists it opens directly; when both exist the user chooses the destination, and no configuration is migrated automatically.