Item detail

microsoft/mcp-gateway

MCP Gateway is Microsoft's reverse proxy and management layer for MCP servers, adding session-aware routing, auth controls, server lifecycle management, and Kubernetes-friendly deployment paths for teams that need more than a single local MCP process.

Score8.9
Popularity78.0
Riskmedium
TierGold
Score breakdown
Usefulness9.0
Novelty8.0
Momentum8.0
Maturity8.5
Open-source/build8.4
Evidence7.2
Workflow potential10.0
Setup ease4.2

Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.

Why it matters

Useful for platform teams that are moving from one-off MCP experiments to shared infrastructure: it gives them a cleaner way to route tool traffic, keep sessions sticky, and manage multiple servers without inventing the control plane from scratch.

Who should use it

platform teamsdeveloper infrastructure engineersMCP server operatorsteams standardizing tool access for agents

Who should skip it

Skip or sandbox it if you cannot review permissions, data access, and failure modes before use.

Risk explanation

This gateway sits in the middle of agent tool traffic and can concentrate access to multiple MCP servers, so review its auth model and deployment boundary before routing sensitive tools through it..

Evidence links

Closest alternatives / related signals

mcpkubernetesai-infrastructuretool-routingplatform-engineering