Skip to content

Support repository-level Copilot CLI MCP configuration #1291

Closed

Description

@pmb5

Describe the feature or problem you'd like to solve

Currently, MCP servers for the CLI can only be configured globally via ~/.copilot/mcp-config.json, VSCode can be per folder/project

Proposed solution

Currently, MCP servers can only be configured globally via ~/.copilot/mcp-config.json.

Feature Request:
Enable repository-level MCP server configuration, similar to LSP servers. This would allow teams to:

  • Share project-specific MCP servers via version control
  • Automatically enable relevant MCP tools when working in specific directories
  • Keep global config clean by only loading servers when needed

Proposed Implementation:

// .github/mcp.json
{
    'servers': {
        'ProjectSpecificServer': {
            'type': 'stdio',
            'command': 'dotnet',
            'args': ['run', '--project', '../mcp-servers/project-mcp/project-mcp.csproj'],
            'env': { 'CONNECTION_STRING': '...' }
        }
    }
}

This would work exactly like the .vscode folder where we can have custom MCP server for each project/folder

Example prompts or workflows

No response

Additional context

No response

Activity

  1. added theissue type on Feb 4, 2026
  2. kawax commented on Feb 5, 2026

    @kawax

    My recommendation

    • .github/mcp-config.json Consistent within Copilot
    • .mcp.json Claude compatible
  3. alexg-c4 commented on Feb 17, 2026

    @alexg-c4

    We already have .vscode/mcp.json in our projects, would be nice if CLI could read this as well.

  4. mrclrchtr commented on Feb 26, 2026

    @mrclrchtr
  5. added
    area:mcpMCP server configuration, discovery, connectivity, OAuth, policy, and registry
    on Apr 6, 2026
  6. examon commented on Apr 7, 2026

    @examon

    This should be resolved as of v0.0.401, which added support for repository-level MCP configuration via .mcp.json at the workspace root. The CLI also reads .vscode/mcp.json and .devcontainer/devcontainer.json, and as of v1.0.11 it discovers these configs from the working directory up to the git root, which covers monorepo setups as well. The specific .github/mcp.json path proposed here is not used as a workspace config source, but .mcp.json provides the same repo-scoped, version-controlled behavior. If you believe there is still a gap, please feel free to reopen this issue.

  7. evr-novicell commented on Apr 10, 2026

    @evr-novicell

    Hmm, as of 1.0.22 I am getting:

    Found .vscode/mcp.json but no .mcp.json. Copilot CLI only reads MCP servers from .mcp.json — consider migrating your config

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

Metadata

Metadata

Assignees

No one assigned

    Labels

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

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions