MCP Servers

[husseinkaraki]

hey - where / how do i add mcp servers?

I see in the readme under /config but isnt explicit where. I do see tools under extrenal-plugins -and tried to create my own following that format but that didnt work. I also tried doing something like

openrouter mcp add-json airtable '{
      "command": "npx",
      "args": ["@rashidazarang/airtable-mcp"],
      "env": {
        "AIRTABLE_TOKEN": "",
        "AIRTABLE_BASE_ID": ""
      }
  }'

to which I got a success message "Added stdio MCP server airtable to local config". but still didnt attach any mcp servers.

[numman-ali]

I'll see what's up

Might need to check where it's installing and where it's getting picked up by the variant

[husseinkaraki]

great. thank you. if you';d like to try, bring codex over to this repo. this may be the kind of bug that codex may be able to handle by itself.

[husseinkaraki]

actually, imma have a go at it with glm4.7 with your cc-mirror harness. code-ception.

[husseinkaraki]

ok. heres a small update. I think I can better describe whats going on. These are mostly DEV EX opportunities, with 1 use case that actually may be an issue.

With claude code, there are 2 sets of configurations, one at the home directory, and one that exists per project. Coming from that thinking, it became easy to assume that this project would follow a similar configuration structure.

The config is centralized, conflicting with the main messaging.
"CC-MIRROR creates isolated Claude Code instances that connect to different AI providers. Each variant has its own config, sessions, themes, and API credentials — completely separate from each other."

While technically not false, coming from claude code where there is both a home and project config, going to a "home" or centralized config, but also it not being global, is kind of like mixing both config methodologies. confusing to me. I dont necessarily have an opinion on whether its better or worse, I just think that it can cause confusion. I recommend being very explicit about the config structure Also, its burried under ~/.cc-mirror/myvariation/config/.claude.json. Adding MCP's servers are a super common use case, so I recommend keeping it in a separate config, like on the same level as variant.json. Claude Code just creates a .claude.json under the home directory.

ok, interesting, so I just ran the same command as above with the -s flag and it added the mcp config to the same file, but at the root of the json.

  "mcpServers": {
    "airtable": {
      "command": "npx",
      "args": [
        "@rashidazarang/airtable-mcp"
      ],

Yeah, I just ran through the setup again, and it doesnt even generate the mcpServers key in the .claude.json file.

So in summary, here are some quick suggestions.

1. Update the readme to describe the configuration structure with explicit detail.
2. Separate the project mcp config files, creating explicit mcp.json file or files (1 should be ok), along with some commented out text that helps again describe your opinionated projects[path/to/project]: { "mcpSevers": { ... approach.
3. How do you actually create a new "project" level config for a specific variant? Ok, great. I can create variants (of different or same LLM providers), but there is a clear config that exists on the system level for that variant, and on a project level. This is probably the most common use case, in that people will probably be using the same set of LLM's most times, and each project has its own set of MCP servers, and potentially other custom configs - thats probably why claude setup their config structure that way - a user, global level config, and a project one. The interactive cc-mirror menu should probably have an option to spin up a project level instance, or what you could also do is, when I run my variant, it could scan that folder for project level files, and if they dont exist, could ask the user if they would like to create them. then it'll create something like .cc-mirror and all the localized project configurations.

just some thoughts. thanks