# jarvis-registry — Secure MCP/Agent Gateway > Jarvis Registry centralizes MCP and A2A access behind OIDC, ACL, and observability—securely proxy tools for copilots. Verified 811★; pushed 2026-05-14. ## Install Merge the JSON below into your `.mcp.json`: ## Quick Use ```bash git clone https://github.com/ascending-llc/jarvis-registry.git cd jarvis-registry cp .env.example .env uv sync --all-packages && source .venv/bin/activate docker compose --profile full up -d open http://localhost:80 ``` ## Intro Jarvis Registry centralizes MCP and A2A access behind OIDC, ACL, and observability—securely proxy tools for copilots. Verified 811★; pushed 2026-05-14. **Best for:** Enterprise teams who need governed tool access for copilots and autonomous agents **Works with:** Docker Compose; OIDC providers; MCP clients over SSE/HTTP (per README) **Setup time:** 15-30 minutes ### Key facts (verified) - GitHub: 811 stars · 101 forks · pushed 2026-05-14. - License: Apache-2.0 · owner avatar + repo URL verified via GitHub API. - README-backed entrypoint: `docker compose`. ## Main - Use Jarvis Registry as your single authenticated entrypoint: proxy MCP/A2A traffic instead of wiring each copilot to each tool. - Configure OIDC first (Keycloak/Cognito/Entra ID), then connect clients and register servers/agents behind the gateway. - Treat ACLs as code: start with least privilege and scope permissions down to tool level as you add integrations. - Turn on tracing/metrics early (OpenTelemetry + Prometheus) so incidents have an audit trail and latency budgets. ### README (excerpt)
Jarvis Registry Logo **Connect any AI copilot or autonomous agent to your enterprise tools — through a single, secure MCP gateway with built-in identity, access control, and full observability.** [![License](https://img.shields.io/github/license/ascending-llc/jarvis-registry?style=flat)](https://github.com/ascending-llc/jarvis-registry/blob/main/LICENSE) [![GitHub release](https://img.shields.io/github/v/release/ascending-llc/jarvis-registry?style=flat&logo=github)](https://github.com/ascending-llc/jarvis-registry/releases) [🚀 Quick Start](#quick-start) | [📖 Documentation](https://jarvisregistry.com/) | [🎬 Demo](https://youtu.be/EUqWc_mAaXs) | [🌐 Website](https://ascendingdc.com/jarvis-ai/jarvis-registry/)
--- ## What is Jarvis Registry? **Jarvis Registry** is an open-source, enterprise-grade **MCP (Model Context Protocol) and A2A Agent Gateway and Workflow Orchestration platform** built by [ASCENDING Inc](https://ascendingdc.com/jarvis-ai/). It solves one of the hardest problems in enterprise AI: giving AI copilots and autonomous agents **secure, governed access** to internal tools and data — without fragmented integrations or security blind spots. | Capability | Description | |---|---| | **MCP Gateway & Reverse Proxy** | Single authenticated entry point for all AI clients and agents using MCP over SSE or Streamable HTTP | | **AI Copilot Integration** | Connect Cursor, Claude Desktop, GitHub Copilot, VS Code, and any MCP-compatible copilot to enterprise tools | | **A2A Agent Orchestration** | Register and manage autonomous agents; orchestrator agents coordinate worker agents through the same secure gateway | | **Identity & Access Management** | OAuth 2.0/OIDC with Keycloak, Amazon Cognito, and Microsoft Entra ID — no custom auth code needed | | **Fine-Grained Access Control** | ACL engine enforces scope-based, role-based permissions down to the individual tool level | | **Skill & Context-Based Discovery** | Semantic search over skills, descriptions, and tags so agents and copilots find the right MCP server or A2A agent at runtime | | **Audit & Observability** | Full request logging, OpenTelemetry tracing, and Prometheus metrics | ### Source-backed notes - README Quick Start uses `uv sync` + `docker compose --profile full up -d`, then opens the UI at `http://localhost:80`. - README lists OAuth 2.0/OIDC integrations (Keycloak, Amazon Cognito, Microsoft Entra ID). - README highlights audit/observability features: request logging, OpenTelemetry tracing, and Prometheus metrics. ### FAQ - **Is it open-source?**: Yes—GitHub license metadata shows Apache-2.0. - **Do I need Docker to try it?**: Docker Compose is the fastest local path per README; Kubernetes is optional for production. - **What clients can connect?**: README mentions MCP-compatible copilots (Cursor/Claude Desktop/VS Code) via gateway transports. ## Source & Thanks > Created by [ascending-llc](https://github.com/ascending-llc). Licensed under Apache-2.0. > > [ascending-llc/jarvis-registry](https://github.com/ascending-llc/jarvis-registry) — ⭐ 811 Thanks to the upstream maintainers and contributors for publishing this work under an open license. --- ## Quick Use ```bash git clone https://github.com/ascending-llc/jarvis-registry.git cd jarvis-registry cp .env.example .env uv sync --all-packages && source .venv/bin/activate docker compose --profile full up -d open http://localhost:80 ``` ## Intro Jarvis Registry 把 MCP/A2A 接入统一到安全网关：OIDC 登录、ACL 权限与可观测性一体化，适合企业把 copilot 工具访问做成可审计代理；已验证 811★，更新于 2026-05-14。 **Best for:** 需要把 copilot/agent 的工具访问做成可审计、可授权的团队 **Works with:** Docker Compose；OIDC 身份提供方；支持 MCP 的客户端（SSE/HTTP，见 README） **Setup time:** 15-30 minutes ### Key facts (verified) - GitHub：811 stars · 101 forks；最近更新 2026-05-14。 - 许可证：Apache-2.0；作者头像与仓库链接均已通过 GitHub API 复核。 - README 中可对照的入口：`docker compose`。 ## Main - 把 Jarvis Registry 当作统一入口：用网关代理 MCP/A2A 流量，而不是让每个 copilot 直连每个工具。 - 先把 OIDC（Keycloak/Cognito/Entra ID）配好，再接入客户端并把 MCP servers/agents 注册到网关后面。 - 把 ACL 当作配置资产：从最小权限开始，逐步细化到单个工具级别的权限边界。 - 尽早开启可观测性（OpenTelemetry + Prometheus），让故障排查有审计链路与延迟数据。 ### README (excerpt)
Jarvis Registry Logo **Connect any AI copilot or autonomous agent to your enterprise tools — through a single, secure MCP gateway with built-in identity, access control, and full observability.** [![License](https://img.shields.io/github/license/ascending-llc/jarvis-registry?style=flat)](https://github.com/ascending-llc/jarvis-registry/blob/main/LICENSE) [![GitHub release](https://img.shields.io/github/v/release/ascending-llc/jarvis-registry?style=flat&logo=github)](https://github.com/ascending-llc/jarvis-registry/releases) [🚀 Quick Start](#quick-start) | [📖 Documentation](https://jarvisregistry.com/) | [🎬 Demo](https://youtu.be/EUqWc_mAaXs) | [🌐 Website](https://ascendingdc.com/jarvis-ai/jarvis-registry/)
--- ## What is Jarvis Registry? **Jarvis Registry** is an open-source, enterprise-grade **MCP (Model Context Protocol) and A2A Agent Gateway and Workflow Orchestration platform** built by [ASCENDING Inc](https://ascendingdc.com/jarvis-ai/). It solves one of the hardest problems in enterprise AI: giving AI copilots and autonomous agents **secure, governed access** to internal tools and data — without fragmented integrations or security blind spots. | Capability | Description | |---|---| | **MCP Gateway & Reverse Proxy** | Single authenticated entry point for all AI clients and agents using MCP over SSE or Streamable HTTP | | **AI Copilot Integration** | Connect Cursor, Claude Desktop, GitHub Copilot, VS Code, and any MCP-compatible copilot to enterprise tools | | **A2A Agent Orchestration** | Register and manage autonomous agents; orchestrator agents coordinate worker agents through the same secure gateway | | **Identity & Access Management** | OAuth 2.0/OIDC with Keycloak, Amazon Cognito, and Microsoft Entra ID — no custom auth code needed | | **Fine-Grained Access Control** | ACL engine enforces scope-based, role-based permissions down to the individual tool level | | **Skill & Context-Based Discovery** | Semantic search over skills, descriptions, and tags so agents and copilots find the right MCP server or A2A agent at runtime | | **Audit & Observability** | Full request logging, OpenTelemetry tracing, and Prometheus metrics | ### Source-backed notes - README 的 Quick Start 使用 `uv sync` 与 `docker compose --profile full up -d`，并在 `http://localhost:80` 打开 UI。 - README 列出 OAuth 2.0/OIDC 集成（Keycloak、Amazon Cognito、Microsoft Entra ID）。 - README 强调审计与可观测性：请求日志、OpenTelemetry tracing 与 Prometheus metrics。 ### FAQ - **它是开源的吗？**：是：GitHub 许可证元数据显示为 Apache-2.0。 - **本地体验必须用 Docker 吗？**：不必须，但 README 推荐 Docker Compose 作为最快路径；生产再考虑 Kubernetes。 - **哪些客户端能接？**：README 提到 Cursor/Claude Desktop/VS Code 等 MCP 客户端，可通过网关传输接入。 ## Source & Thanks > Created by [ascending-llc](https://github.com/ascending-llc). Licensed under Apache-2.0. > > [ascending-llc/jarvis-registry](https://github.com/ascending-llc/jarvis-registry) — ⭐ 811 --- Source: https://tokrepo.com/en/workflows/jarvis-registry-secure-mcp-agent-gateway Author: MCP Hub