mcp-one

mcp-one acts as a unified entry point for multiple MCP servers. It loads a configuration file (mcpone-config.yaml) that describes which mcpServers should be available and how they should be wired together. The project ships with built-in support for various MCP server types and allows you to register additional servers by updating the config file, enabling a single deployment to manage multiple server backends.

To use it locally, start the mcpone process pointing to your config file. The CLI exposes a --config option to specify mcpone-config.yaml and a --baseurl option to set the public listen address. Once running, clients can connect to the mcpone endpoint, and the server will route requests to the appropriate underlying MCP servers defined in the config. You can also add SSE clients at /sse for real-time updates if your frontend requires live streams.

Prerequisites:

• Docker (recommended for the provided deployment method) or a compatible runtime for your chosen deployment method
• Git and a standard shell environment
• Optional: Node.js or Go if you plan to build locally from source

Installation steps (Docker-based):

1. Install Docker on your host following the official instructions for your OS.
2. Pull or build the mcp-one image:
   • If you have a prebuilt image: docker pull localhost/mcp-one:latest
   • If you prefer to build locally, clone the repo and use the provided build workflow to create the Docker image, then tag it as localhost/mcp-one:latest.
3. Prepare your configuration file mcpone-config.yaml describing the mcpServers you want to expose.
4. Run the container: docker run -i --rm localhost/mcp-one:latest -c mcpone-config.yaml --baseurl 0.0.0.0:9090

If you prefer not to use Docker, you can adapt the deployment to your runtime of choice and run the binary directly once you have built it according to the repository’s guidance.

Tips:

• The configuration (mcpone-config.yaml) controls which MCP servers are exposed and how they connect. You can typically add entries for supported servers such as time-mcp and mcp-server-fetch, described in the README, to extend functionality.
• The baseurl option configures where the server listens; ensure firewall rules allow traffic on that port.
• If you encounter issues with docker networking, verify that the container can access any upstream MCP services and that ports are not blocked by your host firewall.
• When adding new MCP servers, keep a consistent YAML schema to avoid parsing errors, and validate syntax before starting the service.