Jarvis Registry is an open-source MCP gateway and A2A agent orchestration platform for enterprise AI, with identity, access control, and observability features. It provides deployment via Docker Compose and a Python-based stack, with multiple releases adding workflow and federation capabilities.
Collecting history — the radar snapshots this repo daily. The trend line appears after 3 days of data (1 so far).
What it is
Jarvis Registry is an open-source, enterprise-grade MCP (Model Context Protocol) and A2A Agent Gateway and Workflow Orchestration platform built by ASCENDING Inc. It enables secure, governed access for AI copilots and autonomous agents to internal tools and data through a single gateway with identity management, access control, and observability.
How it works
The project offers an MCP gateway and reverse proxy acting as a single authenticated entry point for MCP clients and agents using MCP over SSE or Streamable HTTP. It supports AI copilot integrations, A2A agent orchestration, and fine-grained access control with OAuth 2.0/OIDC identity providers (Keycloak, Amazon Cognito, Microsoft Entra ID). It includes audit and observability features such as request logging, OpenTelemetry tracing, and Prometheus metrics. The README describes workflow orchestration that dispatches steps to A2A agents and MCP servers, with a MongoDB-backed runtime state in earlier versions.
Getting started
# Clone the repository
git clone https://github.com/ascending-llc/jarvis-registry.git
cd jarvis-registry
# Copy and configure environment
cp .env.example .env
# Edit .env with your identity provider credentials
# Setup Python Virtual Environment
uv sync --all-packages
source .venv/bin/activate
# Start all services
docker compose --profile full up -d
# Open the registry UI
open http://localhost:80
See the full Get Started guide for detailed instructions.
Recent releases
- asc0.5.4 Jarvis Registry asc0.5.4 (2026-07-29): Features include exposing workflow trigger parameters (initial_input) to all workflow node prompts and enhancements around executor behavior. (#479)
- asc0.5.3 Jarvis Registry asc0.5.3 (2026-07-24): Features include adding Microsoft Azure AI Foundry as a federation provider for Foundry-hosted agents using Microsoft Entra ID authentication. (#377)
- asc0.5.2 Jarvis Registry asc0.5.2 (2026-07-10): Features include wiring up AWS Bedrock AIP for workflow runners, validating environment variables at startup, and consolidating A2A agent configuration by removing the separate agents folder.
- asc0.5.1 Jarvis Registry asc0.5.1 (2026-07-06): Features include workflow creation/update APIs with referencedNodeNames support, and IAM updates to support GroupMember.Read.All and User.ReadBasic.All.
- asc0.3.1 Jarvis Registry asc0.3.1 (2026-05-26): Features include adding a workflow execution engine with MongoDB-backed run state, support for dispatching steps to A2A agents and MCP servers, and runtime control APIs (pause, resume, cancel).
Traction
- Stars: 2767
- Forks: 427
- Open issues: 1
License
- Apache-2.0
Getting started (quick references)
- Docker Compose deployment is supported for a full local stack. The README provides a quick start script snippet above.