Jarvis Registry — Enterprise MCP/A2A Gateway with Identity and Access Control
Source: GitHub — https://github.com/ascending-llc/jarvis-registry (star 2,011, Python, Apache 2.0)
Core Idea
Jarvis Registry is an enterprise-grade MCP and A2A Agent Gateway and Workflow Orchestration platform that connects AI copilots and autonomous agents to enterprise tools through a single secure gateway with built-in identity, access control, and observability.
Key Details
- MCP Gateway and Reverse Proxy — Single authenticated entry point for AI clients using MCP over SSE or Streamable HTTP
- AI Copilot Integration — Connects Cursor, Claude Desktop, GitHub Copilot, VS Code, and any MCP-compatible copilot
- A2A Agent Orchestration — Register and manage autonomous agents; orchestrator agents coordinate worker agents through the same secured gateway
- Enterprise Identity Management — OAuth 2.0/OIDC with Keycloak, Amazon Cognito, Microsoft Entra ID
- Fine-Grained ACL — Scope-based, role-based permissions down to the individual tool level
- Skill and Context-Based Discovery — Semantic search over skills and descriptions so agents find the right MCP server at runtime
- Full Observability — Request logging, OpenTelemetry tracing, Prometheus metrics
- Built on the foundational work of agentic-community/mcp-gateway-registry, evolving it with enterprise features
Why This Matters
Jarvis Registry addresses a key pain point for enterprise AI adoption: giving AI agents secure, governed access to internal tools without fragmented integrations. Its OAuth 2.0/OIDC integration with enterprise IdPs (Keycloak, Cognito, Entra ID) is a differentiator — most AI gateways lack native identity federation. The ACL engine operating at the individual tool level also sets it apart from more permissive gateways.
Relevance to Hermes
Jarvis Registry’s MCP gateway pattern is architecturally similar to Hermes Agent’s MCP server registration system. The identity-aware access control (down to individual tool level) is a feature Hermes could potentially leverage for multi-user or enterprise team deployments where different users should have different tool permissions.