How agentic-community/mcp-gateway-registry works
The repository is the MCP Gateway & Registry: a governed control plane for registering and discovering MCP servers, agents, skills, and other assets, paired with an authenticated gateway data plane. The principal workflow is users or agents connecting through the gateway, which delegates authentication and routes to registered backends; registry APIs manage assets and access policy. The README also documents natural-language discovery, audit, per-user OAuth egress, and A2A discovery. Source excerpts are partial, so unsampled subsystem links are included only where the README documents them.
Main entry points: nginx_service.py nginx gateway · main.py Registry API · server_routes.py Asset routes · server.py Auth server
Components 21
Gateway data plane
- nginx gateway
registry/core/nginx_service.py - Egress OAuth
registry/egress_auth/oauth_engine.py - SSRF protection
registry/utils/url_guard.py
Registry control plane
- Registry API
registry/main.py - Asset routes
registry/api/server_routes.py - Asset services
registry/services/server_service.py - Repository factory
registry/repositories/factory.py - DocumentDB search
registry/repositories/documentdb/search_repository.py - Semantic discovery
registry/services/semantic_search_service.py - Embedding administration
registry/api/embeddings_admin_routes.py - Registry UI
frontend/src/App.tsx
Identity and audit
- Auth server
auth_server/server.py - Access control
registry/auth/dependencies.py - OAuth login
registry/auth/routes.py - Audit logging
registry/audit/service.py
Discovery and federation
- Federation ingestion
registry/services/ard_ingestion_service.py - Travel assistant
agents/a2a/src/travel-assistant-agent/server.py
Other components
- Human users
- AI agents
- MCP and agent backends
- Identity provider
Connections 20
- Human users → nginx gateway: connects through
README.md - AI agents → nginx gateway: connect through
README.md - nginx gateway → Auth server: validates via
README.md - nginx gateway → Registry API: routes to
README.md - nginx gateway → MCP and agent backends: routes to
README.md - Auth server → Identity provider: validates against
README.md - Registry API → Asset routes: registers routes
registry/main.py - Asset routes → Asset services: calls
registry/api/server_routes.py - Asset services → Repository factory: gets repository
registry/services/server_service.py - Repository factory → DocumentDB search: creates search store
registry/repositories/factory.py - Asset routes → Access control: checks access
registry/api/server_routes.py - OAuth login → Auth server: redirects login
registry/auth/routes.py - nginx gateway → Egress OAuth: supports user OAuth
README.md - Registry API → Audit logging: records calls
README.md - Human users → Semantic discovery: discovers assets
README.md - Embedding administration → DocumentDB search: manages embeddings
registry/api/embeddings_admin_routes.py - Federation ingestion → DocumentDB search: indexes ingested assets
registry/services/ard_ingestion_service.py - AI agents → Travel assistant: uses A2A discovery
README.md - Human users → Registry UI: manages assets
README.md - Egress OAuth → SSRF protection: validates URLs
registry/egress_auth/oauth_engine.py