Cette page est affichée en anglais. Une traduction française est en cours.
MCP ConfigsMay 14, 2026·3 min de lecture

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.

MCP Hub
MCP Hub · Community
Prêt pour agents

Cet actif peut être lu et installé directement par les agents

TokRepo expose une commande CLI universelle, un contrat d'installation, le metadata JSON, un plan selon l'adaptateur et le contenu raw pour aider les agents à juger l'adaptation, le risque et les prochaines actions.

Needs Confirmation · 62/100Policy : confirmer
Surface agent
Tout agent MCP/CLI
Type
Mcp
Installation
Git|Uv|Docker
Confiance
Confiance : Established
Point d'entrée
docker compose
Commande CLI universelle
npx tokrepo install 5df6cc08-b682-5112-b25a-82d736b9395b
contrat d'installationJSON metadataplan adaptateurcontenu raw
Introduction

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 GitHub release

🚀 Quick Start | 📖 Documentation | 🎬 Demo | 🌐 Website

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.

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 et remerciements

Created by ascending-llc. Licensed under Apache-2.0.

ascending-llc/jarvis-registry — ⭐ 811

Thanks to the upstream maintainers and contributors for publishing this work under an open license.

Fil de discussion

Connectez-vous pour rejoindre la discussion.
Aucun commentaire pour l'instant. Soyez le premier à partager votre avis.

Actifs similaires

MCP Gateway & Registry — Team Tool Control

MCP Gateway & Registry centralizes MCP servers and agent tools with auth, search, and audit, so teams can manage integrations and scan servers before use.

MCP Configs
MCP Hub

ContextForge — MCP Registry + Proxy Gateway

ContextForge runs an MCP gateway that federates tool servers behind one endpoint, adding governance, auth, and observability for agent tool calls.

MCP Configs
MCP Hub

ToolSDK MCP Registry — Private Gateway + Sandbox

Self-host a private MCP gateway/registry with OpenAPI, sandboxed remote execution and OAuth 2.1, or use @toolsdk.ai/registry to query server configs.

MCP Configs
MCP Hub

Archestra — Secure AI Platform (MCP Governance)

Archestra centralizes MCP servers with governance and observability; verified 3,653★ and ships a Docker quickstart for a private MCP registry.

MCP Configs
Agent Toolkit
◈Accueil🔍Rechercher👤Moi