Claude MCP Manager – A Profile‑Based Server Switcher for the Claude Desktop App

The Claude MCP Manager tackles a common pain point for developers working with AI assistants: juggling multiple Model Context Protocol (MCP) server configurations while keeping sensitive credentials safe. The Claude Desktop application stores all its MCP endpoints in a single JSON file under the user’s Library directory. Whenever a developer wants to switch between different server sets—such as a local experimental cluster, a corporate private endpoint, or a public API—the entire configuration file must be edited by hand. This is error‑prone, difficult to version control, and exposes secrets if the file is shared.

The manager introduces a lightweight command‑line interface that separates server definitions from profiles. Server files are stored in as individual JSON snippets, while profiles—named collections of servers—live in . Activating a profile automatically rewrites the block in Claude’s main config file, restarts the application to apply changes, and records the previous state for easy rollback. By using a dedicated file () to hold API keys and other secrets, the tool lets server definitions reference environment variables with placeholders (). This keeps credentials out of the repository and allows developers to share profiles without leaking sensitive data.

Key capabilities include:

• Declarative server configs: Each MCP endpoint is described in a small JSON file, making it trivial to add, modify, or delete servers without touching the main config.
• Profile management: Group any number of server files into named profiles (, , ). Switching is as simple as typing the profile name.
• Automatic backup and rollback: The tool writes the current block to before applying a new profile, enabling the command to restore the previous state.
• Environment‑aware secrets: Server definitions can reference environment variables or dotenv entries, ensuring that private keys never appear in plain text within the config.
• Developer‑friendly workflow: The CLI exposes commands such as , , and , allowing integration into scripts or CI pipelines.

In real‑world scenarios, a data scientist might maintain a profile pointing to an on‑premise MCP server for rapid prototyping, while a product manager uses a profile that connects to a secure cloud endpoint. When switching between these contexts, the manager updates Claude’s configuration instantly and restarts the app, eliminating downtime or manual edits. The clear separation of concerns also means that teams can version control profile definitions without exposing credentials, and new members can clone the repository and set up their environment with a single command.

Overall, the Claude MCP Manager provides a robust, secure, and developer‑centric solution for managing multiple MCP server configurations on macOS. By automating configuration updates, handling secrets safely, and offering quick rollback, it streamlines the workflow for anyone who relies on Claude Desktop to interact with diverse AI backends.