OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
MCP & Tooling

MCP Gateway

MCP Gateway is a C# reverse proxy and management layer for Model Context Protocol servers in Kubernetes. It routes MCP requests, applies authorization, and manages server and tool-server deployments through a control plane.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

MCP Gateway — OpenViST project profile in MCP & Tooling.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use MCP Gateway when you need a Kubernetes-hosted layer to route MCP traffic and manage MCP server or tool-server deployments. Check client protocol requirements before adopting it, especially when integrating older MCP clients.

Who it is for

  • Teams deploying and operating MCP servers in Kubernetes.
  • Platform developers who need centralized routing and authorization for MCP requests.
  • Teams registering MCP tool servers and managing their deployment lifecycle.

Documented uses

  • Route each MCP request to a ready server instance.
  • Deploy, inspect, update, and remove MCP server adapters.
  • Register tool servers with MCP tool definitions and route tool execution requests.
  • Review adapter status and access server or tool deployment logs.
Before you choose

Requirements & limits

  • The repository documents a local setup using .NET 8, Docker Desktop, Kubernetes, and a local registry.
  • The Azure deployment path requires an Azure subscription with Owner access, Azure CLI, and Entra ID bearer-token setup.
  • The current documented version requires MCP 2026-07-28 clients and adapters and does not include protocol downgrade.
  • Agent and session resources are preview, opt-in features gated by FoundrySettings:Endpoint.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Prepare a local MCP Gateway deployment

Build the gateway and tool-router images and apply the documented local Kubernetes deployment manifests.

Before you start

  • .NET 8 SDK
  • Docker Desktop
  • Kubernetes installed and enabled
  • A local Docker registry

Steps

  1. Start a local registry on port 5000 with the documented Docker command.

  2. Build and push the sample MCP server image to localhost:5000.

  3. Publish the MCP Gateway and Tool Gateway Router images using the repository's .NET publish commands.

  4. Apply deployment/k8s/local-deployment.yml with kubectl and forward the gateway service port to localhost:8000.

Expected outcome

The local Kubernetes deployment is set up with the gateway service port forwarded to localhost:8000.

Guide limitations

  • These steps cover deployment setup; the README's subsequent API test instructions are truncated in the available documentation.
  • The documented version requires MCP 2026-07-28 clients and adapters and does not support legacy initialization, transport sessions, or protocol downgrade.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
12 October 2026
Original website title
microsoft/mcp-gateway · Official homepage title · retained in its source language
How we review sourcesSuggest a correction