MCP Client Configuration Server

This MCP server manages client configurations for multiple MCP-compatible assistants. It provides tooling to retrieve, list, add, and remove server configurations in client configuration files, with automatic file-path detection across Windows and macOS. It enables centralized, scriptable control of how MCP servers are configured for different clients.

How to use

You use this MCP server to manage configuration entries for different MCP clients from a single place. Configure a server once and deploy it to multiple clients, automate repetitive changes, and troubleshoot by listing or inspecting current configurations. You can copy a server configuration from one client to another, ensuring consistent MCP behavior across your setup.

How to install

Prerequisites: Node.js and npm installed on your system. You can verify with node --version and npm --version.

Install the MCP client configuration server globally using npm or run it directly with npx.

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

# Or use npx to run without installing
npx @landicefu/mcp-client-configuration-server

Configuration

To use this MCP server, add it to your MCP settings with the following configuration that runs via npx.

{
  "mcpServers": {
    "mcp-client-configuration": {
      "command": "npx",
      "args": ["-y", "@landicefu/mcp-client-configuration-server"],
      "env": {},
      "disabled": false,
      "alwaysAllow": []
    }
  }
}

Additional sections

Configuration management works across supported MCP clients, including Cline, Roo Code, WindSurf, and Claude desktop. The server stores and edits client MCP settings in a per-client JSON file, automatically creating files and directories when needed. Be aware that unsupported clients will not be present in the configuration set.

Note that you can’t modify certain non-standard MCP configurations through this server. If you attempt to update a server that already exists, you may need to enable explicit overrides in your request.

Troubleshooting tips: ensure the configuration file exists or is creatable, verify the server name you target, and confirm you are using the appropriate client identifier (cline, roo_code, windsurf, claude). If a server is not found, you’ll receive a note indicating the absence rather than a silent failure.

Notes on paths and platforms

Configuration is stored in client-specific files. The server detects the correct path based on your operating system (Windows or macOS) and the client you configure. If a path does not exist, the server will create it and store the updated configuration in a beautified JSON format.

Supported clients for which configurations are maintained include Cline, Roo Code, WindSurf, and Claude. Cursor is not supported due to incompatible configuration storage.

Troubleshooting and best practices

Common issues include missing configuration files or attempting to update a server without enabling override. If you need to add a new server and the file doesn’t exist yet, it will be created automatically. To update an existing server, set allow_override to true in your request.

Best practices: use consistent server names across clients, and consider environment variables for sensitive data in server configurations. Check that you target the correct client before modifying configurations.

Tools and endpoints overview

The MCP server provides a set of utility operations to manage client configurations, including retrieving paths, listing servers, and manipulating individual server configurations.

Available tools

get_configuration_path

Retrieves the absolute path to the configuration file for a specified client (cline, roo_code, windsurf, claude).

get_configuration

Fetches the entire JSON configuration for a specified client.

list_servers

Lists all server names configured in a specified client's configuration.

get_server_configuration

Retrieves the configuration for a specific server in a client's file.

add_server_configuration

Adds or updates a server configuration in a client's configuration file.

remove_server_configuration

Removes a server configuration from a client's configuration file.