MCP Client Configuration Server

🚀 MCP Client Configuration Server

The MCP Server helps manage configurations for different MCP clients. It offers tools to retrieve, list, add, and delete server configurations in client configuration files. The server automatically detects the appropriate operating system (Windows or macOS) and the proper configuration file path for the specified client.

🚀 Quick Start

✨ Features

• Manage MCP servers across multiple clients.
• Automate MCP configuration.
• Facilitate troubleshooting of configured servers and their settings.

📦 Installation

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

# Or run with npx without installation
npx @landicefu/mcp-client-configuration-server

📚 Documentation

Configuration

To use this MCP server in your AI assistant, add it to your MCP settings configuration:

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

Supported Clients

• Cline: Claude-powered code assistant
• Roo Code: Code editor with AI capabilities
• WindSurf: AI-driven browser
• Claude app: Desktop application for Claude AI

⚠️ Important Note

Cursor is no longer supported because it does not use a standard configuration file for MCP settings. Cursor seems to store its MCP configuration in a way that we cannot easily modify, making it incompatible with the file-based approach.

Usage

This server is particularly useful for:

1. Managing MCP servers across multiple clients: Configure the server once and deploy it to multiple clients.
2. Automating configuration: Scripts can use this server to programmatically manage MCP configurations.
3. Troubleshooting: Easily check configured servers and their settings.

🔧 Technical Details

• The server detects the appropriate configuration file path based on the operating system (Windows or macOS) and the specified client.
• All configuration files are saved in a pretty-printed JSON format after modification.
• Error handling is provided for cases where a configuration file cannot be found or accessed.
• If a configuration file does not exist, the server automatically creates it and the required directories.
• The configuration paths for each client are as follows:
  • Windows:
    • Cline: %APPDATA%\Code\User\globalStorage\saoudrizwan.claude-dev\settings\cline_mcp_settings.json
    • Roo Code: %APPDATA%\Code\User\globalStorage\rooveterinaryinc.roo-cline\settings\cline_mcp_settings.json
    • WindSurf: %APPDATA%\WindSurf\mcp_settings.json
    • Claude: %APPDATA%\Claude\claude_desktop_config.json
  • macOS:
    • Cline: ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
    • Roo Code: ~/Library/Application Support/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/cline_mcp_settings.json
    • WindSurf: ~/.codeium/windsurf/mcp_config.json
    • Claude: ~/Library/Application Support/Claude/claude_desktop_config.json

💡 Usage Tip

• Always check if a server exists before updating or deleting it.
• Use consistent server names across clients for easier management.
• Consider using environment variables in server configurations to store sensitive information.

📄 License

No license information provided in the original document.