Skip to the collection

agent-native · Tool Access & Integration · Verified 2026-10-13

MCP Gateway & Registry

Listed on The Agent-Native Index

Unified Agent & MCP Server Registry – Gateway for AI Development Tools

What it does

The MCP Gateway & Registry (agentic-community) is an open-source control plane for organizational AI assets: MCP servers, A2A agents, skills, and custom entity types. Official docs: it began as one secure entry to many MCP servers and grew into a general AI asset registry on the same access-control and audit model.

The gateway is the data plane (nginx: TLS, auth validation, routing). The registry is the control plane (FastAPI: inventory, access model, audit, embeddings). An auth server talks to Keycloak, Entra ID, Okta, Auth0, Cognito, or PingFederate. By default, A2A discovery and ACL happen in the registry and agents then talk peer-to-peer; reverse-proxy mode can force A2A through the gateway.

Distinctness: hosted MCP Gateway is a commercial one-URL tools/skills/sandboxes platform (mcpgateway-sdk). ToolHive runs MCP servers in secure containers. ContextForge federates MCP+A2A+REST/gRPC with UAID routing. This project is the agentic-community enterprise registry (IdP, virtual MCP servers, 3LO egress auth, admission scanning, external-registry federation).


Agent-facing interfaces

How agents onboard

Interaction pattern: CLI + MCP gateway

git clone https://github.com/agentic-community/mcp-gateway-registry.git
cd mcp-gateway-registry
cp .env.example .env
# Set required secrets (KEYCLOAK_ADMIN_PASSWORD, SECRET_KEY, …) — see docs/configuration.md
./build_and_run.sh --prebuilt

See the full onboarding section in the dossier.

Protocol surface

Interface Detail
MCP / HTTPS nginx data plane
REST / OpenAPI Registry API (api/openapi.json)
CLI registry_management.py; ./build_and_run.sh --prebuilt
Deploy Docker Compose, Helm (EKS), Terraform (ECS)
A2A Discovery + optional reverse-proxy mode

Verification

Last verified 2026-10-13.

Sources: