mcp-gateway

This MCP server (the MCP Gateway) provides a multi-tenant, policy-driven proxy surface for MCP tools. It aggregates various upstream tool sources and exposes them per tenant/profile at a dedicated endpoint, enabling secure, scalable access to your internal tools through a streamable HTTP MCP interface. Use the included Web UI and admin tooling to manage tenants, profiles, and tool surfaces, or connect clients directly to the /{profile_id}/mcp endpoint to begin streaming commands to the configured tools. The gateway sits behind adapters and the admin UI, and can route requests to multiple backends (OpenAPI, stdio MCP servers, or HTTP tools) while applying auth, policy, and per-profile transforms.

Prerequisites:

• Docker Desktop or Docker Engine installed and running
• Optional: Docker Compose (if not using the docker compose feature within your Docker CLI)
• Git (to clone or fetch repository assets)

Installation steps:

1. Acquire the repository assets or use the published images via Docker Compose quickstart:

   • Download the quickstart compose file (examples in the README): curl -fsSL -o mcp-gateway-compose.yml https://raw.githubusercontent.com/unrelated-ai/mcp-gateway/main/docker-compose.quickstart.yml

2. Start the stack using Docker Compose (as shown in Quick Start):

   GATEWAY_VERSION=0.10.0 UI_VERSION=0.6.0
   docker compose -f mcp-gateway-compose.yml up -d

   This launches the Gateway, Migrator, and Web UI with the specified component versions.

3. Access the Web UI and endpoints:

   • Web UI: http://127.0.0.1:27102
   • Profile endpoint (example): http://127.0.0.1:27100/<PROFILE_ID>/mcp

4. For development from source, follow the repository's Makefile workflow (see Makefile targets like up / down / up-reset):

   make up make down make up-reset

Note: If you prefer not to use Docker, this project also ships adapters and gateways that can be built from source in Rust; consult the docs for building individual components (adapter/gateway) in Rust if you want a non-Docker setup.

Tips and common issues:

• The Quick Start uses published images; ensure GATEWAY_VERSION and UI_VERSION correspond to desired releases. If you modify versions, re-run the docker compose up to pull new images.
• Use docker compose down to stop the stack; docker compose down -v will also wipe the demo DB volume.
• When developing locally, the Makefile provides targets like make up / make down / make up-reset. Run make help to see all targets.
• The gateway supports multi-tenant configurations via Tenants and Profiles; ensure you configure authentication (API keys, OIDC/JWT) and per-profile tool allowlists to enforce access control.
• If you run into port conflicts, verify that the default ports (e.g., 27100, 27102) are free or customize the compose file to use alternative ports.
• The Adapter exposes MCP at /mcp; the Gateway exposes per-profile MCP endpoints at /{profile_id}/mcp. Ensure client tooling targets the correct endpoint.