Unified Agent & MCP Server Registry – Gateway for AI Development Tools
Agenten stärken
Installation vom Herausgeber. Kein PlugMCP-Endpunkt.
Host a copy with our keys and logs.
Noch kein paketiertes Release in der Registry. Folgen Sie der README des Repositorys.
Remote-URL oder ein Befehl auf Ihrem Rechner? Worin sich die beiden Installationen unterscheiden
Auf PlugMCP ausführen
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
StartenVom Herausgeber
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.
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).
It began as a gateway and registry for the Model Context Protocol (MCP): 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.
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.
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. Onboard third-party OAuth MCP servers, the enterprise way. Because the gateway provides per-user egress authentication, you can connect OAuth-protected SaaS MCP servers such as Slack, Atlassian, and GitHub without every user setting up network access to those services or storing credentials on their laptop. Each user connects their account once; the gateway runs the OAuth (3LO) flow, vaults the per-user token in a secrets manager, and injects it on egress. That collapses onboarding to a single, auditable choke point, so a team can adopt a new SaaS MCP server across the enterprise without per-laptop plumbing or scattered long-lived tokens.
The gateway is the data plane (a generic nginx reverse proxy: TLS, auth validation, routing to backends) and the registry is the control plane (a FastAPI service that owns the inventory, access model, and audit trail, and decides what the gateway may route to). An auth server integrates your identity provider (Keycloak, Entra ID, Okta, Auth0, Cognito, PingFederate) for OAuth2/OIDC, and MongoDB / DocumentDB stores configuration, embeddings, sessions, and audit records. By default, the registry handles A2A discovery, authentication, and access control, and agents then communicate directly (peer-to-peer) rather than routing every call through the gateway. For the full design and its invariants, read the Theory of the System; for layered diagrams, see Architecture Diagrams.
Watch how MCP servers, A2A agents, and external registries work together for dynamic tool discovery:
More walkthroughs are in the demo videos.
The fastest path is the pre-built Docker images. Clone, set a few secrets, and run:
git clone https://github.com/agentic-community/mcp-gateway-registry.git
cd mcp-gateway-registry
cp .env.example .env
# Edit .env and set the required secrets (e.g. KEYCLOAK_ADMIN_PASSWORD, SECRET_KEY).
# See docs/configuration.md for the full list.
nano .env
# Deploy with pre-built images (pulled from Amazon ECR Public by default)
./build_and_run.sh --prebuilt
# Open the Registry UI (served by nginx on port 80)
open http://localhost # macOS (Linux: xdg-open http://localhost)
The Complete Installation Guide has the full walkthrough for Amazon EC2 (prerequisites, MongoDB and Keycloak initialization, first user and service account, registering a server, and testing the gateway).
Deploying somewhere else?
The registry holds four built-in asset types plus admin-defined custom ones, all on one control plane:
SKILL.md skills, with security scanning at registration.Across all of them you get semantic + lexical search, UI, REST, and MCP-native interfaces, and uniform governance. Key features worth calling out:
append_mcp_path: false is now reachable at the bare path it advertises, instead of only the trailing-slash form MCP clients refuse to follow a redirect to. 1.33.0 release notesHTTP_PROXY and HTTPS_PROXY were silently ignored. EGRESS_FORWARD_PROXY_ENABLED=true now routes both through the configured proxy, with the decision coming from DNS classification rather than an operator list: a target is proxied only when every address it resolves to is public, so in-cluster servers keep their IP pin with no configuration. Resolution and classification still run in full before any CONNECT, so the cloud credential, metadata, link-local, reserved and multicast denials still execute, and a request carrying a secret accepts only https so the credential rides inside the tunnel. The cost is stated rather than buried: for a proxied public target, IP-rebind pinning is dropped, since a CONNECT tunnel takes its TLS hostname from the request URL. EGRESS_FORWARD_PROXY_CA_BUNDLE covers a TLS-intercepting proxy, loading the bundle on top of the default roots rather than replacing them. Enabling the flag refuses to start unless NO_PROXY excludes the cloud credential endpoints, because HTTP_PROXY also re-points the AWS SDK. Off by default. 1.32.0 release notes · FAQ: configuring a forward proxy · Operator guideinitialize no longer means parking a static bearer token on the record, where it served health checks, tool discovery, and security scanning alike with no way to scope it to discovery. Those are headless calls with no user behind them, so the registry had nothing else to present. One resolver picks at most one credential from three tiers: a machine client_credentials grant, a per-user OAuth 2.1 identity that an owner consents to once and the registry borrows from the vault, or the gateway's app-only token for obo_exchange servers. A person's own credential and the borrowed identity share a principal, a provider, and a server, so purpose forms part of the vault address and the codec binds it into the AEAD, which keeps the two apart even under a write-capable attacker. A borrowed identity lists tools and never calls one: tools/call never reaches the registry's Python, because nginx proxies it with the caller's own header. A scanner-flagged tool now carries its own block, so one false positive no longer costs the other tools on that server. A block beats admin and wildcard grants, reconciles on rescan so a stale block can clear, and hides the tool from every read projection. Search grades relevance where it used to return a flat 1.0, and in-app latency fell from 641ms to 86ms. Egress calls reuse pooled HTTP clients keyed on the SSRF-validated IP, which keeps pooling rebind-safe. 1.31.0 release notes · Authentication · OBO token exchangemethods: ["all"] grant authorizes no HTTP verb, so nothing gains access by accident. Off by default (GATEWAY_GENERIC_PROXY_ENABLED=false), per-entity opt-in, and no schema migration. Design · Operational Guide · FAQ: call OpenAI or Bedrock through the gateway · FAQ: what an upgrade changes
Older highlights → Feature & Release Highlights · full per-version detail in the release notes and on the GitHub Releases page.The roadmap is best tracked on the GitHub Milestones page. Per-user egress auth (3LO and OBO) and A2A traffic routing shipped in 1.27.0, the gateway for any HTTP resource in 1.30.0, and backend OAuth identity plus per-tool blocking in 1.31.0. At a high level, the big features we're working on next are:
Have a feature request? Please open a GitHub issue, we build in the open.
Full documentation is on the documentation site, and every guide also lives in the docs/ folder. Stuck or have a question? Start with the FAQ / Troubleshooting guide: it covers the most common setup, auth, deployment, and registration issues.
High-traffic pages by audience:
Get started
Platform & security
Architecture & development
Design decisions
The registry collects anonymous, non-sensitive usage telemetry (version, OS, cloud provider, aggregate asset counts) to understand adoption. It is opt-out and on by default; no PII, credentials, endpoints, or model names are ever sent. Disable everything with MCP_TELEMETRY_DISABLED=1. Full schema and privacy guarantees: Telemetry Documentation.
View the full interactive star-growth chart at star-history.com.
Licensed under the Apache-2.0 License. See LICENSE for details.
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 a
Übersicht
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.
Tools
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Kopieren Sie auf dieser Seite die stdio-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
In diesem Eintrag ist keine erforderliche Umgebungsvariable aufgeführt.
MCP Gateway Registry läuft lokal über stdio.
Zuletzt geprüft: 2026-10-27. 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.