Deprecating support for .vscode/mcp.json is a terrible idea
- Lenguaje dominante
- Shell
- Estrellas
- 11.2k
- Forks
- 1.9k
- Merge medio
- 14 h 16 min
- PR fusionados (30 d)
- 6
Descripción
### 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_
Guía de contribución
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- shell, vscode
- Área
- cli, developer-experience
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Estado de actividad
- Tranquilo
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 25/100