# mcp-gateway-registry

> mcp-gateway-registry is an open-source MCP server for agent tooling. Self-hosted gateway and registry that governs MCP servers, agents and skills. It is available on Web, API, CLI and self-hosted.

- **Kind:** MCP server
- **Pricing:** Open source
- **Platforms:** Web, API, CLI, self-hosted
- **Website:** https://agentic-community.github.io/mcp-gateway-registry/
- **Repository:** https://github.com/agentic-community/mcp-gateway-registry
- **GitHub stars:** 1,052
- **License:** Apache-2.0
- **Categories:** [agent tooling](https://ai-powered.com/categories/agent-tooling)
- **Listing updated:** 2026-11-18

## About

The project describes itself as a control plane for AI assets inside an organisation. It began as a gateway and registry for MCP servers and has since added A2A agents, reusable SKILL.md skills and admin-defined custom entity types, all managed from one inventory with shared access rules and an audit trail.

Architecturally, an nginx reverse proxy handles TLS, auth validation and routing, while a FastAPI registry owns the inventory and decides what the gateway may route to. An auth server connects to an existing identity provider such as Keycloak, Entra ID or Okta, and MongoDB or DocumentDB stores configuration, embeddings, sessions and audit records. The README says agents discover each other through the registry and then talk peer-to-peer by default.

The README points at platform and security teams and at developers who want programmatic registration through an OpenAPI spec and Python client. Deployment options named include Amazon EKS with Helm, Amazon ECS with Terraform and Docker Compose on EC2. Telemetry is on by default but can be disabled with an environment variable.

## Features

- **Unified asset registry:** Holds MCP servers, A2A agents, skills and admin-defined custom entity types in one inventory.
- **Single authenticated gateway:** Routes traffic through one entry point that validates OAuth tokens against an existing identity provider.
- **Semantic tool discovery:** Lets agents and coding assistants find tools at runtime through natural-language search.
- **Per-user egress authentication:** Brokers OAuth credentials for third-party SaaS MCP servers so tokens are not stored on laptops.
- **Virtual MCP servers:** Aggregates tools from several backends behind one endpoint with per-tool access control.
- **Audit logging:** Records access and admin events with credential masking for compliance review.

## Good for

- Giving a company one governed entry point to internal MCP servers and agents
- Onboarding OAuth-protected SaaS MCP servers without per-user credential setup
- Letting coding assistants discover approved tools at runtime
- Auditing which AI assets are accessed and by whom

## FAQ

### What license is it released under?

The README and website state it is open source under the Apache-2.0 license.

### Which identity providers does it support?

The README lists Keycloak, Entra ID, Okta, Auth0, Cognito and PingFederate for OAuth2/OIDC.

### Where can it be deployed?

The README names Amazon EKS with Helm, Amazon ECS with Terraform and Docker Compose on Amazon EC2.

### Is telemetry collected?

Anonymous usage telemetry is on by default and can be turned off with MCP_TELEMETRY_DISABLED=1.

### Is mcp-gateway-registry free?

Yes. mcp-gateway-registry is open source, so you can use and self-host it for free.

## Where this comes from

- Description: written from the project's README and the project's website.

## Alternatives

- [toolhive](https://ai-powered.com/mcp/toolhive): toolhive is an open-source MCP server for agent tooling.

---
Source: https://ai-powered.com/mcp/mcp-gateway-registry
