mcp-client-configuration

The MCP Client Configuration Server is a utility for centrally managing MCP server configurations across multiple clients. It exposes a set of operations that let you retrieve, list, add, and remove server configurations stored in each client’s configuration file. The server automatically detects the correct configuration file path based on the target client and the operating system, and it can create missing files or directories as needed. This makes it easy to synchronize server settings across environments like Cline, Roo Code, WindSurf, and Claude app without manually editing files.

Tools provided include: get_configuration_path to locate a client’s config file; get_configuration to fetch the full JSON configuration; list_servers to enumerate configured servers; get_server_configuration to fetch a single server’s configuration; add_server_configuration to add or update a server rule; and remove_server_configuration to delete a server’s entry. These tools enable automation scripts to programmatically configure MCP servers for different clients, streamline troubleshooting, and ensure consistent server management across devices.

Example workflows include exporting a server configuration from one client (e.g., Roo Code) and applying it to another (e.g., Claude desktop) or auditing all configured servers across clients to verify consistency and detect duplicates or conflicts.

Prerequisites:

• Node.js and npm (or npx available with npm)
• Internet access to install packages from npm registry

Install the MCP Client Configuration Server globally:

# Install from npm
npm install -g @landicefu/mcp-client-configuration-server

Run the server directly using npx (no global install required):

npx @landicefu/mcp-client-configuration-server

If you prefer to pin a specific version, specify it after the package name:

npx @landicefu/mcp-client-configuration-server@1.0.0

Verify installation by listing available commands or invoking a help option provided by the CLI (refer to the repository docs for exact CLI usage).

Notes and tips:

• The server stores client configurations in JSON files that are created if missing. If you attempt operations on an unsupported client or an inaccessible path, the tool will emit a descriptive error.
• To update an existing server configuration, set allow_override to true in the operation payload for add_server_configuration.
• Supported OS paths differ by client; the server handles Windows and macOS paths automatically. Linux support is not guaranteed.
• Use consistent server names across clients to simplify management and avoid duplicates.
• Consider environment-specific overrides and sensitive data handling within json_config; use environment variables when possible to avoid embedding secrets in the configuration files.