Central MCP Host

What is Central MCP Host?

Central MCP Host provides a centralized hosting environment for Model Context Protocol (MCP) servers using Docker, Traefik, and SuperGateway. It is designed for developers who need to run multiple MCP servers (Notion, Linear, GitHub, Memory Bank) behind a single reverse proxy with SSE transport.

How to use Central MCP Host?

Clone the repository, copy .env.example to .env and fill in API tokens, then run docker compose up -d. You can start all services or specific ones using Docker Compose profiles (e.g., docker compose --profile github up -d).

Key features of Central MCP Host

• Docker Compose modular structure for easy service addition
• Traefik reverse proxy with path‑based routing
• SuperGateway converts stdio to SSE transport
• Supports Notion, Linear, GitHub, and Memory Bank servers
• Traefik dashboard for monitoring at /dashboard/

Use cases of Central MCP Host

• Run multiple MCP servers in a single Docker environment
• Expose MCP servers via SSE endpoints for remote clients
• Isolate and scale individual MCP services using profiles
• Centralize API token management and network configuration

FAQ from Central MCP Host

What are the prerequisites?

Docker and Docker Compose V2 or later, plus API tokens for the MCP servers you intend to use (Notion, Linear, GitHub).

How do I start only one MCP server?

Use Docker Compose profiles: for example, docker compose --profile github up -d starts only the GitHub server.

How can I test the setup?

Use the MCP Inspector: npx @modelcontextprotocol/inspector node build/index.js.

How do I access the MCP servers once running?

Each server exposes an SSE endpoint and a message endpoint under a path‑based route, e.g., http://$HOSTNAME/notion/sse and http://$HOSTNAME/notion/message. The Traefik dashboard is at http://$HOSTNAME/dashboard/.

What transport does Central MCP Host use?

SuperGateway converts the MCP server’s stdio transport to SSE, which is then proxied by Traefik.