mcp-gateway

Why we included this project

Running several Model Context Protocol servers in production raises a practical question: how do you expose them through one entry point and keep each conversation pinned to the same backend? MCP Gateway is a reverse proxy and control plane for MCP servers that handles this. Requests carrying the same session_id are routed to the same server instance, so stateful sessions stay intact. REST APIs cover the management side, so you can deploy, update, list, and delete MCP servers and registered tools, and a tool gateway router sends each tool call to the backend that defines it. Because it is built around Kubernetes and ships with Azure deployment templates, it fits platform and infrastructure engineers who want a managed, observable entry point for MCP traffic instead of hand-rolling routing and lifecycle logic. The agents-and-sessions preview, which is opt-in, is a useful extra for teams that want to run LLM-driven agents on top of the registered tools.