Kuadrant/mcp-gateway

An envoy-based MCP Gateway that integrates with Istio and policy attachment mechanisms for authN, authZ, rate limiting and more.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 10 minutes ago
Added to GitGenius on May 27th, 2026
Created on July 3rd, 2025
Open Issues & Pull Requests: 91 (-2)
Number of forks: 127
Total Stargazers: 97 (+0)
Total Subscribers: 4 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 19.6 hours
Mean response time: 16.4 days
90th percentile: 60.9 days
Tracked items: 506

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 47% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "enhancement" is answered fastest, typically in about 2 hours, while "area/documentation" waits about 2 weeks. 11% of tracked open issues have had no activity in three months. Only 4% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 72
New in 7 days: 12
Closed in 7 days: 13
Avg open age: 53 days
Stale 30+ days: 43
Stale 90+ days: 8

Recent activity

Opened in 7 days: 11
Closed in 7 days: 13
Comments in 7 days: 15
Events in 7 days: 217

Top labels

  • triage/accepted (273)
  • priority/normal (192)
  • triage/needs-triage (90)
  • priority/low (53)
  • enhancement (46)
  • good first issue (39)
  • area/documentation (38)
  • area/testing (31)

Detailed Description

MCP Gateway is an Envoy-based API gateway that aggregates and routes multiple Model Context Protocol servers behind a single endpoint.

The tool solves the problem of managing multiple MCP servers by providing a unified gateway that can route requests to different MCP server instances. It integrates with Istio and Kubernetes Gateway API to enable policy attachment for authentication, authorization, rate limiting, and other traffic management concerns. The architecture consists of a broker and router deployment alongside a controller that manages the gateway configuration through custom resources.

Adoption suits teams running Kubernetes clusters who need to expose multiple MCP servers through a single managed endpoint with policy enforcement. The tool works best in environments already using Istio or Gateway API, though a minimal installation option exists for clusters with only Gateway API support. The project provides both a quick-start development environment using kind and a production-oriented installation path. Local development includes integration with Keycloak for OAuth setup and MCP Inspector for testing connectivity.

The project receives issue reports from both core maintainers and external users, indicating real-world adoption without excessive support burden. Maintainers typically respond to new issues and pull requests within a day. Development work concentrates on documentation, enhancements, and testing infrastructure.