$git clone https://github.com/agentic-community/mcp-gateway-registryUnified Agent & MCP Server Registry – Gateway for AI Development Tools
| 1 | <!-- Budget: 350 lines max (CI-enforced). Feature announcements -> docs/overview/feature-release-highlights.md (top 3 mirrored here). Structure rationale -> docs/design/theory-of-the-system.md#6-how-to-change-this-system-without-breaking-its-theory --> |
| 2 | <div align="center"> |
| 3 | <img src="docs/img/mcp_gateway_horizontal_white_logo.png" alt="MCP Gateway & Registry Logo" width="100%"> |
| 4 | |
| 5 | **Unified Agent & MCP Server Registry – Gateway for AI Development Tools** |
| 6 | |
| 7 | [](https://github.com/agentic-community/mcp-gateway-registry/stargazers) |
| 8 | [](https://github.com/agentic-community/mcp-gateway-registry/network) |
| 9 | [](LICENSE) |
| 10 | [](https://github.com/agentic-community/mcp-gateway-registry/releases) |
| 11 | |
| 12 | [Get Running Now](#quick-start) | [Docs](https://agentic-community.github.io/mcp-gateway-registry/) | [Executive Brief](docs/overview/executive-brief.md) | [Slide Deck](docs/slides/mcp-gateway-registry-presentation.pdf) | [Demo Videos](docs/demo-videos.md) | [AWS Workshop](https://catalog.us-east-1.prod.workshops.aws/workshops/0c3265a6-1a4a-467b-ae56-e4d019184b0e/en-US) | [Community](#community) |
| 13 | |
| 14 | </div> |
| 15 | |
| 16 | --- |
| 17 | |
| 18 | The **MCP Gateway & Registry** is a single, governed control plane for every AI asset in your organization, from MCP servers and AI agents to skills and any custom asset your teams build. It is open source, licensed under Apache 2.0, and runs on Kubernetes (Amazon EKS), fully managed serverless (Amazon ECS), or Docker Compose (Amazon EC2). |
| 19 | |
| 20 | It began as a gateway and registry for the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/introduction): one secure entry point to many MCP servers, with centralized discovery and governance. As teams started registering agents, skills, and other assets alongside their servers, it grew into a general-purpose **AI asset registry** on the same gateway, access-control, and audit model it started with. |
| 21 | |
| 22 | ## Why we built this |
| 23 | |
| 24 | Without a control plane, every team wires its own MCP servers and agents by hand: separate credentials in every dotfile, no shared inventory, no audit trail, and no way to discover or govern what exists. Agents can't find other agents; servers and agents live in separate registries that can't share policy. |
| 25 | |
| 26 | This platform replaces that with **one governed entry point for every AI asset**. Register a server, agent, skill, or custom entity once; discover it by natural-language search; reach it through a single authenticated gateway that enforces access and records every call. One control plane, one access model, one audit trail, across all asset types. |
| 27 | |
| 28 | ``` |
| 29 | ┌─────────────────────────────────────┐ ┌──────────────────────────────────────────────────────┐ |
| 30 | │ BEFORE: Chaos │ │ AFTER: MCP Gateway & Registry │ |
| 31 | ├─────────────────────────────────────┤ ├──────────────────────────────────────────────────────┤ |
| 32 | │ │ │ │ |
| 33 | │ Developer 1 ──┬──► MCP Server A │ │ Developer 1 ──┐ ┌─ MCP Server A │ |
| 34 | │ ├──► MCP Server B │ │ │ ├─ MCP Server B │ |
| 35 | │ └──► MCP Server C │ │ Developer 2 ──┼──► MCP Gateway │ │ |
| 36 | │ │ │ │ & Registry ───┼─ MCP Server C │ |
| 37 | │ Developer 2 ──┬──► MCP Server A │ ──► │ AI Agent 1 ───┘ │ │ │ |
| 38 | │ ├──► MCP Server D │ │ │ ├─ AI Agent 1 │ |