Skip to content

Add support for repo-specific / folder-specific MCP configs #288

@rishitank

Description

@rishitank

Describe the feature or problem you'd like to solve

I want to be able to support sourcing the MCP configuration from multiple sources - ideally a global config and a project-specific config. The reason for this is that for some projects I need specific MCP servers e.g. neo4j memory MCP server, whereas for other projects it would not be applicable (or would have a different neo4j MCP server config for example).

Proposed solution

A simple solution would be to provide a repeatable --mcp-config flag that would be able to source a MCP config from multiple places and internally you could concatenate the MCP configuration. This could also work by having the global MCP config in your ~/.copilot directory being loaded automatically, with support for additional source of MCP configurations.

Example prompts or workflows

When starting a new session I would say:
Read your neo4j memory to understand the structure, patterns, rules and features of this codebase, all the previous work that has been implemented so far and all the learnings that have come from it.

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions