RepoRadar
Leave a Tip
Item detail

agentic-community/mcp-gateway-registry

The MCP Gateway and Registry is an Apache-2.0 enterprise pattern for centralising Model Context Protocol servers behind a single authenticated, observable surface. It bundles OAuth (Entra ID, Okta, Auth0), fine-grained access control, dynamic tool discovery, and a registry UI so platform teams can ship internal MCP servers without each team re-implementing auth.

Open source →Back to radar
Score7.5
Popularity70.0
Riskconditional
TierGold
Score breakdown
Usefulness8.0
Novelty7.0
Momentum7.0
Maturity7.0
Open-source/build8.4
Evidence7.2
Workflow potential9.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 want to ship internal MCP servers to the rest of the org: stand up the gateway, register a pilot server, wire it up to your existing IdP, and walk the access-control log to confirm a single user cannot accidentally reach a tool they should not have.

Who should use it

internal developer platform teamsenterprise AI platform ownerssecurity teams reviewing MCP rolloutsMCP server authors who need an easy auth story

Who should skip it

Skip for now if you need a low-setup, non-technical tool today.

Risk explanation

a gateway is a high-value target; lock down admin paths, monitor for unusual tool-call patterns, and review OAuth client secret handling before production; fine-grained access control is only useful if the registry is the actual source of truth; treat shadow MCP servers as a real risk.

Evidence links

Closest alternatives / related signals

mcpgatewayregistryoauthenterpriseagent-platform