mcp-all-in-one

mcp-all-in-one is a powerful MCP service aggregator that merges multiple MCP services into a single unified MCP interface. It provides multi-protocol support (stdio and HTTP) and includes built-in self-configuration tools, enabling dynamic configuration and real-time validation without manual edits. With the unified server, clients can interact with a single entry point while the underlying calls are transparently proxied to the appropriate backend MCP services. This makes managing multiple MCP tools and integrations simpler and more consistent across environments.

To use it, configure mcp-all-in-one in your MCP client as shown in the Quick Start. You can add the server with npx or via a client JSON configuration, for example: a client like Claude Code can add the server using an npx command that registers mcp-all-in-one@latest stdio. Once configured, you can manage and configure the connected MCP services through mcp-all-in-one’s self-configuration tools, adjust tool availability, and monitor status from a single control point. The tools support dynamic management, configuration validation, and auto-reconnect behavior to keep services available even after transient failures.

Prerequisites:

• Node.js (recommended LTS) and npm installed
• Access to the internet to fetch packages

Installation options:

1. Quick start with npx (no global install needed):

• Ensure you have npm/Yarn available
• Run: npx -y mcp-all-in-one@latest stdio

2. Install locally (npm):

• Create a project folder and navigate into it
• Run: npm init -y npm i -D mcp-all-in-one
• Start the server with Node (see mcp_config example): npx mcp-all-in-one@latest stdio

3. Global installation (optional, for frequent use):

• Run: npm install -g mcp-all-in-one
• Start the server with: mcp-all-in-one stdio

Notes:

• The server can be launched in stdio mode or other supported modes as documented.
• If using Windows, ensure your shell handles command execution correctly as noted in the feature set.

Tips and caveats:

• The server supports self-configuration; you can add, modify, and validate MCP tool configurations at runtime.
• When using multi-service aggregation, ensure each backend MCP service is reachable and adheres to the MCP protocol expectations.
• If you encounter connectivity issues, enable auto-reconnect in the config and check status monitoring dashboards.
• Environment variables can be used to customize behavior (e.g., logging level, backend timeouts) depending on deployment. Refer to the official docs for a full list of options.
• For client integrations, the Quick Start examples show how to register mcp-all-in-one in Claude Code and other clients; adapt the command to your environment if necessary.