The read half — `get_configuration_path`, `get_configuration`, `list_servers`, `get_server_configuration` — is convenience; the write half is a real capability, because `add_server_configuration` accepts an arbitrary `json_config` and `allow_override` decides whether it replaces an entry that is already registered. Grant that deliberately: an agent able to add a server configuration to a client can also add one you did not choose, and `remove_server_configuration` takes a name with no confirmation step in its signature.
A configuration manager for MCP clients: 6 tools that locate a client's configuration file, read it whole or entry by entry, and add, overwrite or remove a server entry within it.
- The file's location before anything else: `get_configuration_path` returns the path to the configuration file for a named `client`.
- The whole file when you need the surrounding context: `get_configuration` returns a client's entire configuration.
- A registry view rather than raw JSON: `list_servers` returns the server names configured in a client.
- One entry at a time when that is all you need: `get_server_configuration` returns the configuration for a single `server_name` within a client.
- Writes with the overwrite decision made explicit: `add_server_configuration` takes a `json_config` for a `server_name` plus an `allow_override` flag that decides whether an entry already there is replaced.
- Removal by name: `remove_server_configuration` takes a `client` and a `server_name` and deletes that entry.
No account and no key. What it does need is filesystem access to the configuration file of the `client` you name, since the tools read from and write to that file directly.
One command — npx -y @landicefu/mcp-client-configuration-server