Activity

1. andrewkcchung

   added

   triage

   on Apr 28, 2026
2. andrewkcchung

   added the

   Bug

   issue type on Apr 28, 2026
3. examon

   added

   area:mcpMCP server configuration, discovery, connectivity, OAuth, policy, and registryMCP server configuration, discovery, connectivity, OAuth, policy, and registry

   area:configurationConfig files, instruction files, settings, and environment variablesConfig files, instruction files, settings, and environment variables

   and removed

   triage

   on Apr 28, 2026
4. JohnLBergqvist commented on Apr 29, 2026

   

   JohnLBergqvist

   on Apr 29, 2026

   Last edited by JohnLBergqvist

   More actions

   Copilot CLI points us to this document, which says that we should use .mcp.json (which VSCode doesn't support) instead of .vscode/mcp.json (both at the project root) - i've summarised the 3 locations below.

   MCP Configuration Locations for GitHub Copilot CLI

   Summary

   File	Scope	Key	Read by
   ~/.mcp-config.json	User-level	"mcpServers"	Copilot CLI only
   .mcp.json (project root)	Project-level	"mcpServers"	Copilot CLI only
   .vscode/mcp.json (project root)	Project-level	"servers"	VS Code only

   Notes

   • Copilot reads both ~/.mcp-config.json (user-level) and .mcp.json (project-level) simultaneously.
   • As of Copilot CLI v1.0.39, .vscode/mcp.json is no longer read by the Copilot CLI, even if present in the project root.
   • VS Code only picks up .vscode/mcp.json — it does not read .mcp.json or ~/.mcp-config.json.
   • There is no shared cross-client config file format between VS Code and Copilot CLI.
5. stephbu commented on May 1, 2026

   

   stephbu

   on May 1, 2026

   Last edited by stephbu

   More actions

   Thinking about our copilot usage...

   • I want to layer user, org, and project configurations
   • I'd add VS into the toolchain mix here too
   • I want one format, that I can compose to reflect organization, team and project objectives, that works across all toolchains.
6. vinaysingh7 commented on May 4, 2026

   

   vinaysingh7

   on May 4, 2026

   More actions

   Copilot CLI points us to this document, which says that we should use .mcp.json (which VSCode doesn't support) instead of .vscode/mcp.json (both at the project root) - i've summarised the 3 locations below.

   MCP Configuration Locations for GitHub Copilot CLI

   Summary

   File Scope Key Read by
   ~/.mcp-config.json User-level "mcpServers" Copilot CLI only
   .mcp.json (project root) Project-level "mcpServers" Copilot CLI only
   .vscode/mcp.json (project root) Project-level "servers" VS Code only

   Notes

   • Copilot reads both ~/.mcp-config.json (user-level) and .mcp.json (project-level) simultaneously.
   • As of Copilot CLI v1.0.39, .vscode/mcp.json is no longer read by the Copilot CLI, even if present in the project root.
   • VS Code only picks up .vscode/mcp.json — it does not read .mcp.json or ~/.mcp-config.json.
   • There is no shared cross-client config file format between VS Code and Copilot CLI.

   Now I see vscode referring .mcp.json (project root) Project-level as well. But it cannot customize mcp servers(like enable/disable) from this location
7. ivklgn

   added a commit that references this issue on Sep 22, 2026

   fix: copilot host wiring targeted surfaces Copilot CLI does not read

   ...

   9f74d3b