mcp-manager

MCP Manager for Claude Desktop provides a client-side GUI to configure and launch MCP servers that integrate with the Claude Desktop application. It focuses on making it easy to manage multiple MCP servers by letting you paste and save the exact commands needed to start each server, as well as the required environment variables. The app surfaces a curated list of popular MCP endpoints you can enable or customize, and it generates ready-to-run command blocks so you can copy-paste them into your terminal. Use the built-in configuration components to tailor each server's environment and runtime so Claude can securely access the data sources, APIs, and tools you enable through MCP.

Prerequisites:

• A MacOS machine with administrative access
• Node.js installed (the MCP Manager UI is written in React/TypeScript and uses Bun for development; a compatible Node/Bun setup is recommended)
• Access to the internet to install dependencies

Installation steps:

1. Clone the MCP Manager repository: git clone https://github.com/your-org/mcp-manager.git cd mcp-manager

2. Install dependencies (example using Bun): bun install

3. Start the development server: bun dev

4. Build for production when ready: bun run build

Note: If you prefer a Node-based workflow instead of Bun, you can install dependencies with npm/yarn as appropriate and adjust the project scripts accordingly. The README suggests Bun as the primary build tool for this project.

Tips and considerations:

• This is a client-side tool; your MCP server configurations are stored locally in your environment and not uploaded to any central server.
• You can copy terminal commands directly from the UI for quick installation or runtime configuration of each MCP server.
• Environment variables for each MCP server should be defined in the UI (or in the generated command blocks) to ensure proper authentication and access control.
• Common issues include missing dependencies for specific MCP servers, incorrect environment variable names, or network access restrictions. Double-check the required vars and endpoints for each server you enable.
• If fetch, time, or Sentry integrations are needed, verify network permissions and ensure any required tokens or DSNs are provided as env vars.
• The project uses Bun as the primary tooling; if you switch to Node or another package manager, ensure consistency with your chosen environment and update the scripts accordingly.