mcp-config

MCP Config is a CLI tool to manage MCP server configurations for MCP clients. It acts as a central repository and launcher for various MCP servers, allowing you to quickly view, configure, add, or remove server configurations that you use with MCP clients. The tool detects available servers from its internal repository and provides an interactive prompt to perform actions such as configuring a server, viewing its details, or removing it. You can also directly add a new server by selecting from the repository or by invoking the tool with a server name (for example, npx mcp-config llamacloud) to install that server in one step. This makes it straightforward to switch between different MCP server setups without manual setup each time.

Prerequisites:

• Node.js and npm installed on your system
• Access to the internet to fetch dependencies

Installation steps:

1. Clone the repository (or install directly if you’re using the published package):

git clone <repository-url>
cd mcp-config

2. Install dependencies:

npm install

3. Build the project (if a build step is defined):

npm run build

4. Start the tool (development or production as appropriate):

npm run start

Usage examples:

• Run the tool with the default prompt: npx mcp-config or start from the built binary if applicable
• Add a new server from the repository: npx mcp-config and follow the interactive prompts
• Install a specific server directly: npx mcp-config llamacloud

Notes and tips:

• The tool supports multiple MCP servers such as Claude, Windsurf, and Cursor. It maintains a local repository of server configurations and provides a one-line install for adding new servers.
• If you encounter issues with a particular server configuration, use the View Details option to inspect its settings, or remove and re-add the server to refresh its configuration.
• Ensure your environment variables or API keys required by specific MCP servers are set in your shell or an env file before launching the tool (where applicable).
• The command examples assume the package name is mcp-config; if your setup uses a different registry or package scope, adjust accordingly.
• When using npx, the -y flag in some workflows can skip prompts; you can omit it to allow interactive prompts if you prefer.