agentic-community/mcp-gateway-registry

Enterprise-ready MCP Gateway & Registry that centralizes AI development tools with secure OAuth authentication, dynamic tool discovery, and unified access for both autonomous AI agents and AI coding assistants. Transform scattered MCP server chaos into governed, auditable tool access with Keycloak/Entra integration.

What it solves

This project provides a centralized control plane for managing AI assets across an organization. It eliminates "credential sprawl" and the chaos of manual wiring where developers and agents must manage separate credentials and connections for every MCP server or AI agent they use. By providing a single, governed entry point, it ensures that AI tools are discoverable, secure, and auditable.

How it works

The system consists of a data plane (an nginx reverse proxy) and a control plane (a FastAPI service). The data plane handles TLS, authentication validation, and routing to backends. The control plane manages the inventory of assets, access models, and audit trails. It integrates with identity providers (like Okta or Keycloak) for OAuth2/OIDC and uses MongoDB/DocumentDB for storage.

Assets can be registered as MCP servers, A2A agents, skills, or custom entities. The gateway can act as a proxy for any HTTP backend, including model inference endpoints (like OpenAI or Bedrock), allowing the registry to inject credentials at egress so they never reside on a user's local machine.

Who it’s for

  • Developers looking to integrate AI coding assistants and programmatic access to AI tools.
  • Platform, security, and ops teams who need to manage deployment, authentication, and access control for AI assets at scale.
  • Decision-makers evaluating how to adopt AI tools within an enterprise environment.

Highlights

  • Unified AI Gateway: A single authenticated entry point for MCP servers, model inference, A2A agents, and generic REST endpoints.
  • Dynamic Tool Discovery: Enables agents and assistants to find tools at runtime using natural-language semantic search.
  • Per-User Egress Auth: Brokers third-party SaaS credentials (OAuth 3LO) so tokens are stored in a secrets manager rather than on user laptops.
  • Virtual MCP Servers: Aggregates tools from multiple backends into a single endpoint with per-tool access control.
  • Enterprise Governance: Includes security scanning for registered assets, a fail-closed admission gate, and full audit logging for compliance.
  • Federation: Ability to pull in external registries, such as Anthropic's MCP Registry or AWS Agent Registry.

Related

  • Project
  • Project
  • Project
  • Project
  • Project