Thanks for the suggestion. This will be available in the next version. Each project now has a new setting in Project settings > AI providers: "Leave this project's .mcp.json untouched". When you turn it on, AgentsRoom stops writing to your .mcp.json, removes only the entries it had added itself, and no longer adds the file to .gitignore. Your own servers (including URLs with changing query parameters) stay exactly as committed. Claude Code and Copilot agents still get the AgentsRoom tools, which are now passed through their launch command. Restart any running agents after you switch it on. If this isn't what you had in mind, let us know and we'll adjust it.
Add an option to preserve project-level .mcp.json configuration
From AnonymousDone 1 day ago
Recently, the Minimal System Prompt option was added, which is a great improvement. As a follow-up, it would be useful to have a similar setting to control whether AgentsRoom should override the project's .mcp.json file.
Some projects already define their own MCP servers in .mcp.json. Currently, AgentsRoom can remove these configurations and modify .gitignore, potentially breaking the project's intended setup and affecting the repository's existing configuration.
Configuring MCP servers in AgentsRoom's settings is not always a viable alternative, especially when a server URL includes dynamic query parameters that frequently change. For example:
https://mcp.server.com/mcp?version=2.7.3&project=xyz
Proposed solution: Add a setting that allows users to choose whether AgentsRoom should manage or override .mcp.json, or preserve the project's existing configuration without modifying it.
This would make it possible to use AgentsRoom with projects that rely on custom MCP configurations while keeping their original setup intact.