Test: Workspace-root MCP configuration entry points
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- node.js, typescript
- Domain
- developer-experience, testing
Research direction
Start with a disposable workspace and follow the listed MCP: Add Server and MCP: Open Workspace Folder MCP Configuration steps. Verify root .mcp.json creation, server placement, direct opening when it is the only file, and picker behavior when it coexists with .vscode/mcp.json. Done means the expected root and legacy-file behavior passes without automatic migration.
Written by the indexing model from the issue text.
Description
Refs: #335551
- anyOS
Complexity: 2
Authors: @vritant24
Verification steps
-
Open a disposable folder that does not contain
.mcp.jsonor.vscode/mcp.json. -
Run MCP: Add Server and add a Command (stdio) server:
npx -y @modelcontextprotocol/server-everything -
Choose Workspace (folder-name) as the destination.
-
Verify:
- A
.mcp.jsonfile is created at the workspace root. - The server is written under
mcpServers. - No
.vscode/mcp.jsonfile is created.
- A
-
Run MCP: Open Workspace Folder MCP Configuration.
-
Verify the root
.mcp.jsonopens directly without a file picker.
Root and legacy files together
- Create
.vscode/mcp.jsonin the same folder with a different server. - Run MCP: Add Server again and choose Workspace (folder-name).
- Verify you can choose between the root
.mcp.jsonand legacy.vscode/mcp.json. - Choose one file and complete the addition.
- Verify the new server is added only to the selected file and the other file remains unchanged.
- Run MCP: Open Workspace Folder MCP Configuration.
- 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.
- Dominant language
- TypeScript
- Stars
- 193k
- Forks
- 43.2k
- Avg merge
- 9h 46m
- Merged PRs (30d)
- 669
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/vscode
-
# [copilot] convertToApiChatMessage silently drops Document content parts — PDF attachments never reach LanguageModelChatProvider extensionsPossibly taken @vritant24 claimed this 9 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
microsoft/vscode#336694 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Native MDM ignores documented object-form plugin marketplacesPossibly taken @rwoll claimed this 9 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
microsoft/vscode#333816 · 1 assignee ·
Maintainers usually reply within 1 day
-
stale triage-needed
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
All issues in microsoft/vscode
Similar issues
-
check:passed streams:add
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Fission-AI/OpenSpec#1986 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
nestjs/docs.nestjs.com#3554 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
publicodes/publicodes#868 ·
-
namespace operations
Difficulty 1/5 Under an hour Newbie friendliness 78/100
EclipseFdn/open-vsx.org#13488 ·
Maintainers usually reply within 2 days