Jarvis Registry is a gateway and registry for Model Context Protocol (MCP) servers and Agent-to-Agent (A2A) agents. It sits between AI clients and internal tools so that copilots and autonomous agents reach enterprise systems through one authenticated entry point rather than through per-tool integrations. The gateway speaks MCP over SSE and Streamable HTTP and proxies requests to registered backends.
Authentication uses OAuth 2.0 and OIDC with Keycloak, Amazon Cognito, or Microsoft Entra ID. An access-control-list engine applies scope- and role-based permissions down to individual tools. Registered MCP servers and A2A agents are discoverable through semantic search over skills, descriptions, and tags, and orchestrator agents can coordinate worker agents through the same gateway. Every request is logged, with OpenTelemetry tracing and Prometheus metrics for observability.
The project derives from the agentic-community mcp-gateway-registry project. It runs locally with Docker Compose and has deployment guides for EKS, AKS, and GKE, plus federation with AWS AgentCore and Azure AI Foundry.
Features
- MCP gateway and reverse proxy: one authenticated endpoint for all MCP clients over SSE or Streamable HTTP
- Copilot integration: connects Cursor, Claude Desktop, GitHub Copilot, VS Code, and other MCP clients to internal tools
- A2A orchestration: registers autonomous agents and lets orchestrator agents coordinate workers through the gateway
- Identity providers: OAuth 2.0 and OIDC through Keycloak, Amazon Cognito, and Microsoft Entra ID
- Fine-grained ACLs: scope- and role-based permissions enforced per tool
- Semantic discovery: search over skills, descriptions, and tags to find the right server or agent at runtime
- Observability: request logging, OpenTelemetry traces, and Prometheus metrics
- Federation: integrates with AWS AgentCore and Azure AI Foundry agent platforms
- Cloud deployment: guides for EKS, AKS, GKE, and a Docker Compose local stack
