Summary

Jarvis Registry addresses the challenge of securely connecting AI copilot and autonomous agents to enterprise tools. It provides a unified, secure gateway with built-in identity, access control, and observability, enabling governed access to internal resources without fragmented integrations or security blind spots. This platform is designed for enterprises seeking robust control over their AI agent interactions.

How It Works

The platform functions as an enterprise-grade MCP (Model Context Protocol) and A2A Agent Gateway, orchestrating workflows through a single, secure entry point. It leverages MCP over SSE or Streamable HTTP, integrating directly with popular AI copilots like Cursor and GitHub Copilot, as well as custom autonomous agents. Authentication is handled via OAuth 2.0/OIDC with enterprise IdPs (Keycloak, Cognito, Entra ID), enforcing fine-grained, role-based access control (RBAC) down to individual tool permissions. Runtime discovery of agent skills and context is facilitated through semantic search, while comprehensive audit logs, OpenTelemetry tracing, and Prometheus metrics ensure full observability.

Quick Start & Requirements

Installation involves cloning the repository, configuring environment variables from .env.example, setting up a Python virtual environment using uv, and starting services with docker compose --profile full up -d. Key prerequisites include Docker and an identity provider configured in .env.

• Quick Start Guide
• Full Documentation
• Demo Video

Highlighted Details

• Supports integration with major AI copilots (Cursor, Claude Desktop, GitHub Copilot, VS Code) and any MCP-compatible client.
• Offers robust identity management via Keycloak, Amazon Cognito, and Microsoft Entra ID.
• Implements fine-grained access control (ACL) for granular permission enforcement.
• Provides extensive observability features including request logging, OpenTelemetry tracing, and Prometheus metrics.

Maintenance & Community

The project welcomes contributions via a dedicated guide. Security vulnerabilities should be reported directly to support@ascendingdc.com. The project acknowledges foundational work from agentic-community/mcp-gateway-registry. No specific community channels (e.g., Slack, Discord) are listed.

Licensing & Compatibility

Licensed under the permissive Apache 2.0 License, allowing for broad compatibility with commercial and closed-source applications.

Limitations & Caveats

The provided README does not detail specific limitations, unsupported platforms, or known bugs, suggesting a focus on core enterprise functionality.