Skip to content

Document Copilot CLI MCP server discovery #10245

Description

@ntrogh

Product change

VS Code can discover MCP server configurations from the Copilot CLI configuration file. Discovery checks COPILOT_HOME before the default ~/.copilot/mcp-config.json location, uses the corresponding locations in remote environments, and is disabled by default through chat.mcp.discovery.enabled.copilot.

Why the docs need an update

The MCP configuration guidance describes automatic server discovery but does not identify Copilot CLI as a discovery source, explain its file locations and precedence, or state that this source is opt-in.

Suggested documentation

  • docs/agents/reference/mcp-configuration.md: Add Copilot CLI to automatic MCP discovery, including the supported configuration locations, precedence, remote behavior, and opt-in setting.
  • docs/agents/reference/ai-settings.md: Add the discovery setting and its default if the setting is not already generated or listed.

Details to verify

  • Setting: chat.mcp.discovery.enabled.copilot.
  • Default: false.
  • Configuration source: COPILOT_HOME or ~/.copilot/mcp-config.json.
  • Remote sessions use the corresponding paths in the remote environment.

Acceptance criteria

  • MCP documentation identifies Copilot CLI as a supported discovery source.
  • The configuration locations, precedence, remote behavior, setting name, and default are accurate.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions