jarvis-registry

Why we included this project

For teams wiring AI assistants into internal systems, Jarvis Registry offers one controlled door instead of dozens of point-to-point integrations. It sits between your copilots or autonomous agents and the MCP servers or A2A agents that reach company tools, so every call passes through a single place. That entry point also handles the security side: OAuth and OIDC with providers like Keycloak and Entra ID decide who gets in, and an ACL engine can restrict access down to individual tools rather than trusting everything wholesale. It keeps a full record of what happened, with request logs, OpenTelemetry tracing, and Prometheus metrics, the kind of audit trail enterprises usually need before letting agents touch production data. Organizations running mixed tooling, such as Cursor, Claude Desktop, GitHub Copilot, or VS Code alongside orchestrated agents, will find this a practical way to govern and observe those workloads without writing custom auth glue.