Landicefu MCP Client Configuration Server

🚀 MCP Client Configuration Server

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

🚀 Quick Start

📦 Installation

# Install from npm
npm install -g @landawn/mcp-config-server

# Or use yarn
yarn add @landawn/mcp-config-server

⚙️ Configuration

To use this server as a dependency, ensure it is correctly installed. For detailed information on configuration and usage, refer to the project documentation.

🖥️ Supported Clients

📋 Use Cases

• Data Synchronization: Synchronize configurations across multiple clients to ensure consistency.
• Centralized Management: Manage all client configurations in one place for easy maintenance and updates.
• Version Control: Incorporate configuration files into a version control system to record change history.

💻 Usage Examples

📖 Basic Usage

Retrieve Configuration

const { getConfig } = require('@landawn/mcp-config-server');

getConfig('cline', 'existing-server').then(config => {
    console.log('Retrieved configuration:', config);
}).catch(err => {
    console.error('Error retrieving configuration:', err);
});

List All Servers

const { listConfigs } = require('@landawn/mcp-config-server');

listConfigs('cline').then(servers => {
    console.log('List of servers:', servers);
}).catch(err => {
    console.error('Error listing configurations:', err);
});

Add a New Server

const { addConfig } = require('@landawn/mcp-config-server');

addConfig('cline', 'new-server', {
    "api-key": "your-api-key",
    "endpoint": "http://localhost:3000"
}).then(message => {
    console.log('Success message:', message);
}).catch(err => {
    console.error('Error adding configuration:', err);
});

Update an Existing Server

const { updateConfig } = require('@landawn/mcp-config-server');

updateConfig('cline', 'existing-server', {
    "allow_override": true,
    "new-setting": "value"
}).then(config => {
    console.log('Updated configuration:', config);
}).catch(err => {
    console.error('Error updating configuration:', err);
});

Delete a Server

const { removeConfig } = require('@landawn/mcp-config-server');

removeConfig('cline', 'existing-server').then(message => {
    console.log('Success message:', message);
}).catch(err => {
    console.error('Error removing configuration:', err);
});

🔧 Technical Details

• The server automatically detects the configuration file path based on the operating system and the specified client.
• All configuration files are saved in a beautified JSON format after modification.
• Error handling is provided, with corresponding prompts for situations such as missing configuration files.
• Configuration files and directories are automatically created if they do not exist.

❓ Frequently Asked Questions

Configuration File Not Found

• Configuration files are automatically created when adding a new server.
• Error messages are displayed for other operations when the configuration file is not found.

Server Already Exists

• Set allow_override to true when updating an existing server.
• Example:

{
    "client": "cline",
    "server_name": "existing-server",
    "json_config": { /* New configuration */ },
    "allow_override": true
}

Unsupported Platform

• Currently, only Windows and macOS are supported.
• Linux support may be added in future versions.

💡 Best Practices

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