mcp-manager

MCP Server Manager is a web-based GUI tool designed to help you control Model Context Protocol (MCP) servers used with Claude and Cursor. It provides toggle switches to enable or disable individual MCP servers and their associated tools, automatically syncing configuration changes between Claude and Cursor. With this utility, you can quickly view which tools are available for each server and securely manage environment variables and API keys that these tools rely on. The interface focuses on simplicity while ensuring your MCP configurations stay consistent across platforms.

To use it, install and run the MCP Server Manager, then navigate to the server you want to configure. Use the on-screen toggle to enable or disable that server, and adjust the listed tools as needed. After making changes, click Save Changes to apply the configuration, and restart Claude (as prompted or required by your setup) to activate the new settings. The tool emphasizes secure handling of sensitive data like API keys and environment variables, so review those values in the env section for each server before enabling it.

Prerequisites:

• Node.js and npm installed on your system
• Access to the project repository for this MCP server

Installation steps:

1. Clone the repository git clone https://github.com/yourusername/mcp-manager.git cd mcp-manager

2. Install dependencies npm install

3. Create a configuration file (copy from example) cp config.example.json config.json

4. Start the server npm start

5. Open the web interface in your browser http://localhost:3456

Notes:

• Ensure any required environment variables are set in config.json under the env field for each MCP server.
• If you change server paths or ports, update the configuration accordingly and restart the application.

Tips and common considerations:

• Validate environment variables (like API keys) before enabling a server to avoid runtime errors.
• Keep the MCP configuration files synced between Claude and Cursor to prevent desynchronization issues.
• If you see a blank page or connection errors, check the npm start output for port binding issues or missing dependencies.
• The tool supports multiple MCP servers; you can enable/disable them independently as needed.
• Ensure paths in the config.json are accessible by the user running the MCP Server Manager.