MCP.so
Sign In

MCP One

@MCPHubCloud

Basic information

Category

Other

License

MIT

Transports

stdio

Author

MCPHubCloud

About MCP One

A unified All-in-One entrance for mcpservers, which manages various types of mcpservers.

MCP One config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "mcp-one": {
      "command": "docker",
      "args": [
        "run",
        "-it",
        "--rm",
        "localhost/mcp-one:latest"
      ]
    }
  }
}

MCP One tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is mcp-one?

mcp-one is a unified all-in-one entrance for MCP servers that manages various types of rated MCP servers. It allows users to run a single server that aggregates multiple MCP tools and resources, then exposes them over SSE to compatible clients like Cherry Studio or Cursor.

How to use mcp-one?

Configure a YAML file listing the MCP servers you want to aggregate, then run ./mcp-one -c mcpone-config.yaml --baseurl 0.0.0.0:9090. Point your MCP client (e.g., Cherry Studio, Cursor) to http://localhost:9090/sse. Pre-built binaries and a Docker image are available; you can also build from source using make build or make dockerbuild.

Key features of mcp-one

  • Single entry point for multiple MCP servers
  • Supports adding custom MCP servers via YAML config
  • Exposes combined server over SSE transport
  • Runs as a standalone binary or Docker container
  • Community-driven with PR and issue contributions welcome

Use cases of mcp-one

  • Use one SSE endpoint instead of configuring many separate MCP servers
  • Combine time, fetch, and other tools into one service for a client
  • Host a single MCP gateway on a server for multiple users
  • Rapidly prototype and test multiple MCP servers locally

Frequently asked questions

1

What does mcp-one actually do?

It runs a single MCP server that embeds and manages multiple other MCP servers, exposing them all through one SSE connection.

2

Which MCP servers are supported by default?

Currently `time-mcp` and `mcp-server-fetch` are included; you can add any MCP server in the `mcpserver-config.yaml` file.

3

How do I add a new MCP server to mcp-one?

Edit the YAML configuration file to list the new server’s command, arguments, and environment variables, similar to how you would configure it in a client.

4

Do I need any runtime besides the binary?

No, the compiled binary includes everything needed. If using Docker, only Docker is required.

5

How do I expose mcp-one to the internet?

Run it with `--baseurl 0.0.0.0:9090` (or any public address) and ensure the port is reachable. The SSE endpoint will be at `<host>:<port>/sse`.

Comments

More Other MCP servers