Deprecating support for .vscode/mcp.json is a terrible idea
- Dominant language
- Shell
- Stars
- 11.2k
- Forks
- 1.9k
- Avg merge
- 14h 16m
- Merged PRs (30d)
- 6
Description
### Describe the bug
I just tried using the CLI and hit this:
[Deprecation of vscode mcp json](https://docs.github.com/en/copilot/reference/copilot-cli-reference/cli-command-reference#migrating-from-vscodemcpjson)
I use that mcp.json all the time in VS code. Now I need two mcp.json files?
### Affected version
_No response_
### Steps to reproduce the behavior
_No response_
### Expected behavior
_No response_
### Additional context
_No response_
Contributor guide
Research direction
Start with the linked migration guidance and review how the CLI currently handles .vscode/mcp.json versus its replacement configuration. Confirm the intended compatibility behavior and identify the relevant configuration discovery and documentation entry points. Done means the issue has a decided, tested approach that avoids requiring duplicate mcp.json files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell, vscode
- Domain
- cli, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100