mcpserver.so LogoMCPFly
Submit
Central MCP Host logo

Central MCP Host

by odgrim

IntegrationDockerTraefikSuperGatewaySSEReverse Proxy

This project provides a centralized hosting environment for Model Context Protocol (MCP) servers using Docker, Traefik, and SuperGateway. It allows you to interact with various services like Notion, Linear, and GitHub through a unified interface.

View on GitHub

Last updated: N/A

What is Central MCP Host?

Central MCP Host is a Docker-based environment that centralizes the hosting of Model Context Protocol (MCP) servers. It uses Traefik as a reverse proxy to route requests to different MCP servers and SuperGateway to convert between stdio and SSE transports.

How to use Central MCP Host?

  1. Clone the repository. 2. Copy .env.example to .env and fill in your API tokens. 3. Start the services using docker compose up -d. 4. Access the services via their respective path-based routes (e.g., /notion/sse, /github/message).

Key features of Central MCP Host

  • Centralized hosting for MCP servers

  • Docker Compose based setup

  • Traefik reverse proxy for routing

  • SuperGateway for transport conversion (stdio to SSE)

  • Modular Docker Compose structure for easy service management

Use cases of Central MCP Host

  • Integrating Notion with other services

  • Connecting Linear tickets to other workflows

  • Interacting with GitHub repositories programmatically

  • Creating a unified interface for multiple MCP servers

  • Recording project notes and learnings

FAQ from Central MCP Host

What is MCP?

MCP stands for Model Context Protocol, a protocol for interacting with various services and data sources.

What is SuperGateway?

SuperGateway converts between stdio and SSE transports, enabling MCP servers to communicate with clients using SSE.

How do I add a new MCP server?

Create a new Docker Compose file in the docker-compose directory for your service and configure Traefik routing accordingly.

How do I access the Traefik dashboard?

The Traefik dashboard is accessible at http://$HOSTNAME/dashboard/.

How do I troubleshoot path routing issues?

Verify the path prefixes in Traefik labels, SuperGateway baseUrl option, and strip middleware configuration.