mcp-gateway
Universal-MCP-Gateway (mcp-gateway)
Ein leistungsfähiger, Multi-Tenant-fähiger Reverse-Proxy- und Gateway-Dienst für das Model Context Protocol (MCP), basierend auf @thargy/mcp-server-core.
Warum mcp-gateway?
Die meisten Drittanbieter-MCP-Server (wie github-mcp-server, Brave Search, SQLite, PostgreSQL) sind in erster Linie für die lokale Desktop-Ausführung über stdio konzipiert. Wenn sie über HTTP oder Cloudflare-Zero-Trust-Tunnel bereitgestellt werden, fehlen ihnen oft:
Cloudflare-SSE-Stream-Priming: Sofortige
: heartbeat\n\n-Kommentare, um die Pufferung durch den Reverse-Proxy zu umgehen.Moderne-MCP-Handshake-Kompatibilität: Unterstützung für
subscriptions/listen,server/discoverund zustandslosen JSON-RPC-Dispatch.Verwaltung des Sitzungslebenszyklus: Korrekte-Verfolgung des
Mcp-Session-Id-Headers und Token-Authentifizierung.
mcp-gateway fungiert als ein einzelner, Multi-Tenant-fähiger Adapter zwischen entfernten MCP-Clients (wie Antigravity-IDE, Cloudflare-Zero-Trust, Cursor) und einem oder mehreren vorgeschalteten Drittanbieter-MCP-Backends (Container, HTTP-APIs oder stdio-CLI-Tools).
Related MCP server: Shared MCP Gateway
Architektur
graph TD
subgraph Clients ["MCP Clients"]
AG["Antigravity IDE / Agents"]
CFPortal["Cloudflare Zero Trust MCP Portal"]
end
subgraph Ingress ["Cloudflare Tunnel (mcp.thargy.com)"]
Tunnel["cloudflared (HA Server)"]
end
subgraph Gateway ["mcp-gateway Container (:3007 -> :3008)"]
App["@thargy/mcp-server-core Router"]
GHRoute["/gh/mcp -> HttpProxyAdapter"]
BraveRoute["/brave/mcp -> StdioProxyAdapter"]
end
subgraph Backends ["3rd-Party Backends"]
GHContainer["github-mcp-backend (:8082)"]
BraveCLI["@modelcontextprotocol/server-brave-search"]
end
Clients --> Ingress
Ingress --> Gateway
App --> GHRoute --> GHContainer
App --> BraveRoute --> BraveCLIKonfiguration (config.yaml)
port: 3008
routes:
gh:
type: http
name: "github-mcp-server"
description: "GitHub Model Context Protocol Server (repositories, commits, issues, PRs)"
targetUrl: "http://github-mcp-backend:8082"
authHeaderEnv: "GITHUB_PERSONAL_ACCESS_TOKEN"
# brave:
# type: stdio
# name: "brave-search"
# description: "Brave Search MCP Server"
# command: "npx"
# args: ["-y", "@modelcontextprotocol/server-brave-search"]
# env:
# BRAVE_API_KEY: "${BRAVE_API_KEY}"This server cannot be deployed
Maintenance
Related MCP Connectors
Governed MCP gateway: one endpoint for your tools, with credential custody and audit log.
Managed MCP gateway with OAuth, per-agent permissions, shared accounts and activity logs.
Stateless MCP gateway and OTel span-streaming bridge for hosted MCP servers.
MCP Gateway: wrap any MCP server with cold-start retries, uptime SLA, and per-execution MPP billing.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceGateway MCP Server - Route MCP requests intelligently to multiple backend servers.3MIT
- FlicenseNot gradedqualityDmaintenanceAggregates multiple shared MCP servers into a single HTTP gateway, providing a unified, observable, and reusable MCP access layer for multiple AI clients like Codex, OpenCode, and OpenClaw. It centralizes configuration management, logging, health checks, and circuit breaking to simplify multi-client MCP deployments.5-
- AlicenseNot gradedqualityCmaintenanceA universal MCP server that acts as a unified gateway for dynamically connecting and managing multiple MCP servers via a single HTTP endpoint.6 npm6MIT
- AlicenseNot gradedqualityAmaintenanceA universal MCP gateway that aggregates multiple MCP servers into a single endpoint, providing features like hot-reload, auto-healing, and a hook system for request/response mutation.1MIT