René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Add support for repo-specific / folder-specific MCP configs","articleBody":"### Describe the feature or problem you'd like to solve\n\nI 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).\n\n### Proposed solution\n\nA 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.\n\n### Example prompts or workflows\n\nWhen starting a new session I would say:\nRead 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.\n\n### Additional context\n\n_No response_","author":{"url":"https://github.com/rishitank","@type":"Person","name":"rishitank"},"datePublished":"2025-10-13T10:47:12Z","url":"https://github.com/github/copilot-cli/issues/288"}