Action Required: Migrate Your Copilot CLI MCP Config Away from .vscode/mcp.json
The GitHub Copilot CLI has removed its incomplete support for .vscode/mcp.json configuration files. It now exclusively reads Model Context Protocol (MCP) server definitions from dedicated files. These files are .mcp.json in your project's root or .github/mcp.json within your repository. Your existing .vscode/mcp.json file will continue to function for VS Code itself. The key differences between the VS Code and Copilot CLI formats are the top-level key and the requirement for a type field. For the Copilot CLI, the top-level key should be mcpServers, and each server entry needs a type, like "local" or "http". To migrate, locate your .vscode/mcp.json, then create a new .mcp.json file with the adjusted format. Alternatively, you can place the converted content in .github/mcp.json for broader repository access. After creating the new file, verify the migration by running copilot mcp list in the relevant directory. This ensures your MCP servers are recognized and the startup warning message disappears. Remember to repeat this migration process for every project that uses a .vscode/mcp.json file.