Two instances with different `MCP_CONFIG_PATH` values is the practical setup: one editing the AWS Q Developer file, one editing Claude Desktop's. Backups plus atomic writes mean a malformed edit costs you a restore rather than a broken client, and `validate_config` will tell you which it was before you restart anything.
A configuration editor for MCP config files — the JSON that lists which servers a client loads. It reads, edits and validates that file for AWS Q Developer or Claude Desktop, and backs it up before every change.
- `list_servers` shows every server currently configured, and `get_server` returns one entry by name
- `add_server` adds an entry with its command, args and env; `update_server` edits one, merging environment variables by default or replacing them when you pass `replace_env`
- `remove_server` deletes an entry
- `validate_config` checks the file's structure and contents, and `export_config` dumps the whole configuration as JSON
- Every change is written atomically and preceded by a timestamped backup
The Python package mcp-conf-mcp-server, version 0.1.0, run with `uvx --from git+https://github.com/r3-yamauchi/mcp-conf-mcp-server.git mcp-conf-mcp-server`, or installed with `pip install -e .`. It edits `~/.aws/amazonq/mcp.json` unless you point `MCP_CONFIG_PATH` somewhere else — set it to the Claude Desktop config path to manage that instead. `MCP_BACKUP_DIR` moves the backups; by default they land in a `backups/` folder beside the config. `~`, `%APPDATA%` and `%USERPROFILE%` are expanded for you.