Jarvis Registry
A unified MCP gateway for governed enterprise-tool access by copilots and autonomous agents.
What does this agent do, and when should you use it?
Jarvis Registry is an open-source enterprise MCP (Model Context Protocol) and A2A agent gateway and workflow orchestration platform from ASCENDING Inc. Its MCP Gateway & Reverse Proxy provides a single authenticated entry point for MCP clients and agents over SSE or Streamable HTTP. The platform can register and manage autonomous agents, with orchestrator agents coordinating worker agents through that same gateway. Its identity layer supports OAuth 2.0/OIDC integration with Keycloak, Amazon Cognito, and Microsoft Entra ID, while its ACL engine enforces scope-, role-, and individual-tool-level permissions. A full local stack can be deployed with Docker Compose, and the project also documents deployment guides for AWS EKS, Azure AKS, and GCP GKE.
After deployment, the MCP Gateway & Reverse Proxy accepts AI-client and agent traffic using MCP over SSE or Streamable HTTP and acts as the unified authentication entry point. It integrates OAuth 2.0/OIDC with Keycloak, Amazon Cognito, or Microsoft Entra ID, then uses its ACL engine to enforce access by scope, role, and individual tool. The registry registers and manages autonomous A2A agents; orchestrator agents can coordinate worker agents through the same secure gateway. It also performs semantic search across skills, descriptions, and tags to discover an MCP server or A2A agent, and provides request logging, OpenTelemetry tracing, and Prometheus metrics.
- A platform team wants Cursor, Claude Desktop, GitHub Copilot, or VS Code to reach internal tools through one authenticated MCP entry point.
- A security team needs AI-tool permissions tied to Keycloak, Amazon Cognito, or Microsoft Entra ID and enforced down to individual tools.
- An automation team is building an autonomous-agent workflow that needs registered A2A agents and an orchestrator coordinating worker agents.
- An organization with multiple MCP servers needs runtime discovery based on skills, descriptions, and tags.
- An operations team needs request logs, OpenTelemetry traces, and Prometheus metrics for copilot and agent traffic.
What are this agent's strengths and limitations?
- One MCP Gateway & Reverse Proxy covers both SSE and Streamable HTTP instead of requiring separate client-facing entry points.
- OAuth 2.0/OIDC integrations are explicitly named for Keycloak, Amazon Cognito, and Microsoft Entra ID, with ACL enforcement by scope, role, and individual tool.
- The same platform covers MCP-server discovery plus A2A agent registration, management, and orchestration.
- Request logging, OpenTelemetry tracing, and Prometheus metrics are built into the stated observability model.
- A full local deployment depends on Python, uv, Docker Compose, and configured identity-provider credentials.
- The README does not provide concrete MCP client configuration, API/CLI commands, agent-registration procedures, or end-to-end tool-call examples.
- Only Keycloak, Amazon Cognito, and Microsoft Entra ID are explicitly named as identity integrations; support for other providers is not evidenced.
- Although EKS, AKS, and GKE deployment guides are listed, the supplied material does not specify their configuration, scaling model, or failure-handling behavior.
How do you install or deploy this agent?
Prerequisites explicitly shown are Python, uv, Docker Compose, and identity-provider credentials. Run:
git clone https://github.com/ascending-llc/jarvis-registry.git
cd jarvis-registry
cp .env.example .env
# Configure identity-provider credentials in .env
uv sync --all-packages
source .venv/bin/activate
docker compose --profile full up -d
When the full local stack is running, open http://localhost:80.
How do you use this agent?
The first documented working action is to configure identity-provider credentials in .env, start the full Docker Compose profile, and open http://localhost:80. The README states that the gateway accepts MCP over SSE or Streamable HTTP and names Cursor, Claude Desktop, GitHub Copilot, and VS Code as integrations. It does not provide copyable MCP client configuration, agent-registration steps, tool-call examples, or API/CLI invocation details, so those first integration actions cannot be reproduced from the supplied material alone.
How does this agent compare with similar options?
The README says Jarvis Registry builds on foundational work from agentic-community/mcp-gateway-registry and positions this project as an enterprise evolution with identity, access control, observability, and A2A orchestration capabilities.