ascending-llc/jarvis-registry

What it solves

Jarvis Registry addresses the challenge of providing AI copilots and autonomous agents with secure, governed access to internal enterprise tools and data. It eliminates the need for fragmented integrations and removes security blind spots by acting as a centralized gateway.

How it works

It functions as an MCP (Model Context Protocol) and A2A (Agent-to-Agent) gateway and reverse proxy. It provides a single authenticated entry point for AI clients using MCP over SSE or Streamable HTTP. The system integrates with identity providers like Keycloak, Amazon Cognito, and Microsoft Entra ID for authentication, and uses an ACL engine to enforce role-based and scope-based permissions at the tool level.

Who it’s for

Enterprise organizations that need to connect AI copilots (such as Cursor, Claude Desktop, and GitHub Copilot) or autonomous agents to their internal infrastructure while maintaining strict security, identity management, and observability.

Highlights

• Centralized Gateway: A single entry point for all MCP-compatible copilots and agents.
• Identity Management: Built-in support for OAuth 2.0/OIDC via major identity providers.
• Fine-Grained Control: Tool-level access control lists (ACLs) for precise permissioning.
• Agent Orchestration: Ability to register and manage worker agents coordinated by orchestrator agents.
• Semantic Discovery: Searchable skills, descriptions, and tags to help agents find the right tools at runtime.
• Observability: Full request logging, OpenTelemetry tracing, and Prometheus metrics.