one

One MCP is a centralized management interface for MCP services. It acts as a proxy layer that helps you discover, install, configure, and monitor MCP services from a unified dashboard. The platform supports service groups, analytics, multi-user authentication via OAuth (GitHub and Google), and flexible deployment with SQLite (default), MySQL, or PostgreSQL, with optional Redis caching. Use the web UI to browse a marketplace or add custom MCP services, configure each service, group multiple services into a single endpoint, and monitor usage and health in real time.

Prerequisites:

• Docker (recommended) or a Go toolchain if you prefer building from source
• Optional: Docker Compose for orchestrated setup

Option A – Deploy with Docker (recommended):

# Pull the latest image (example tag)
docker pull buru2020/one-mcp:latest

# Run the container (port 3000 exposed, data persisted to ./data)
docker run -d \
  --name one-mcp \
  -p 3000:3000 \
  -v $(pwd)/data:/data \
  buru2020/one-mcp:latest

Access the application at http://localhost:3000

Option B – Manual Go build (local development):

# Clone the repository
git clone https://github.com/burugo/one-mcp.git
cd one-mcp

# Prerequisites: Go 1.19+
# Build the backend and frontend as appropriate (examples may vary by repo layout)
# Build backend
cd backend
go build ./...

# Run the server (port 3000 by default)
PORT=3000 ./one-mcp

Configuration notes: create a runtime config file if desired at ~/.config/one-mcp/config.ini and populate settings such as PORT, SQLITE_PATH, SQL_DSN, and REDIS_CONN_STRING. The default login in manual setups is username: root, password: 123456. If you use Docker, environment variables can override config values as needed.

Tips and common issues:

• If using Docker, ensure data persistence by mounting a host directory (e.g., -v $(pwd)/data:/data).
• For production, consider using MySQL or PostgreSQL instead of the default SQLite, and enable Redis for caching.
• OAuth setup (GitHub/Google) helps avoid API rate limits when querying npm or marketplace data.
• The runtime configuration priority is defaults < config.ini < environment variables < flags; command-line flags have the highest precedence.
• When upgrading, re-create or migrate database schemas as needed and verify that ports (default 3000) are available.
• If you encounter a login prompt, ensure you are using the correct default credentials or configure a proper user via the API once authenticated.