Currently, the config resolution will take the first file found in this order:
MCP_CONFIG_PATH environment variable
-c/--config command line argument
./mcp_servers.json (current directory)
~/.mcp_servers.json
~/.config/mcp/mcp_servers.json
Sometimes I want to use both my personal MCP servers and the project's MCP servers. E.g. I might want the AI agent to write a task to my personal Todo app (say Todoist) so I remember to work on this Playwright issue. I would prefer to store the Todoist MCP in my user config (e.g. ~/.config/mcp/mcp_servers.json), but the Playwright MCP is project-related and shared between my teammates and would go into the workspace config (e.g. ./mcp_servers.json). This currently cannot be done.
Is it possible to implement a merge of the configuration files instead? Same-named ones would be overwritten (which would cater for MCP hiding, e.g., my personal GitHub MCP can be hidden by my company's GitHub MCP).
Currently, the config resolution will take the first file found in this order:
MCP_CONFIG_PATHenvironment variable-c/--configcommand line argument./mcp_servers.json(current directory)~/.mcp_servers.json~/.config/mcp/mcp_servers.jsonSometimes I want to use both my personal MCP servers and the project's MCP servers. E.g. I might want the AI agent to write a task to my personal Todo app (say Todoist) so I remember to work on this Playwright issue. I would prefer to store the Todoist MCP in my user config (e.g.
~/.config/mcp/mcp_servers.json), but the Playwright MCP is project-related and shared between my teammates and would go into the workspace config (e.g../mcp_servers.json). This currently cannot be done.Is it possible to implement a merge of the configuration files instead? Same-named ones would be overwritten (which would cater for MCP hiding, e.g., my personal GitHub MCP can be hidden by my company's GitHub MCP).