logo

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 ↓Open shareable report →

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 hours ago
Type:Server / PlatformCategory(s):Service Mesh, API Gateways & Load BalancersMCP Servers, Agent Skills & PromptsCloud Native & Infrastructure
Added to GitGenius on May 27th, 2026
Created on July 3rd, 2025
Open Issues & Pull Requests: 98 (+0)
GitHub issues: Enabled
Number of forks: 139
Total Stargazers: 105 (+0)
Total Subscribers: 4 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 21.4 hours
Mean response time: 15.4 days
90th percentile: 50.1 days
Tracked items: 571

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

Maintainer activity

28 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 11, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits.

How this project is maintained

About 3% of issues opened in the past year have never received a reply. 53% 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 6 hours, while "area/documentation" waits about 10 days. 17% of tracked open issues have had no activity in three months. 83% of issues opened in the past year have been closed, leaving a working backlog.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 80
New in 7 days: 5
Closed in 7 days: 6
Avg open age: 44 days
Stale 30+ days: 45
Stale 90+ days: 28

Recent activity

Opened in 7 days: 1
Closed in 7 days: 5
Comments in 7 days: 8
Events in 7 days: 31

Top labels

  • triage/accepted (322)
  • priority/normal (218)
  • triage/needs-triage (95)
  • enhancement (71)
  • priority/low (59)
  • area/maintenance (45)
  • area/documentation (40)
  • good first issue (39)

Most active issues this week

Sign in to see which issues are moving.
Sign in
Explore full issue details

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.