Skip to content

Jarvis Registry

Jarvis Registry Logo **Connect any AI copilot or autonomous agent to your enterprise tools — through a single, secure gateway with protocol-compliant MCP and A2A support, built-in identity governance, and full observability.**

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.

Jarvis Registry acts as a centralized control plane that sits between your AI clients (copilots, IDEs, agents) and your enterprise MCP servers. Every request is authenticated against your Identity Provider (Keycloak, Amazon Cognito, or Microsoft Entra ID) and checked against fine-grained ACL policies — before a single tool is invoked.

Whether you are plugging your favorite AI copilot (Claude, OpenAI, or Jarvis Chat) into internal APIs, orchestrating fleets of autonomous A2A agents, or federating tools across cloud environments, Jarvis Registry gives you the security, discoverability, and auditability that enterprise deployments demand.

See It in Action

What It Does

Capability Description
Gateway & Proxy Single authenticated entry point for all AI clients and agents — supports MCP transports (SSE, Streamable HTTP) and A2A agent transports (JSON-RPC 2.0 over HTTP, HTTP+JSON); routing, rate limiting, and policy enforcement flow directly from the Registry
Registry Compliance enforcement layer for MCP servers and A2A agents — validates AgentCard schema, MCP tool declarations, and transport compliance (JSON-RPC 2.0, HTTP+JSON); tracks A2A spec version per agent and stores custom discovery paths and auth prerequisites; the single source of truth the gateway derives every invocation decision from
AI Copilot Integration Connect Cursor, Claude Desktop, GitHub Copilot, VS Code, and any MCP-compatible copilot to enterprise tools
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
A2A Agent Workflow Register and manage autonomous agents; orchestrator agents coordinate worker agents through the same secure gateway
Identity & Access Management Governance enforcement layer that sits above your IdP (Keycloak, Cognito, Entra ID, Okta) — manages per-agent OAuth 2.0/OIDC auth prerequisites, Client Credentials (M2M) flows, and RBAC mappings, then propagates the enforced policy to the gateway
Fine-Grained Access Control ACL engine enforces scope-based, role-based permissions down to the individual tool level
Audit & Observability Full request logging, OpenTelemetry tracing, and Prometheus metrics

Architecture Overview

flowchart LR
    subgraph Clients["① AI Entry Points"]
        Copilot["AI Copilot\n(Claude / OpenAI / Jarvis Chat\nCursor / GitHub Copilot)"]
        A2AAgent["A2A Agents\n(Orchestrator + Workers)"]
    end

    subgraph JarvisGW["Jarvis Registry"]
        direction TB

        Discovery["② Skill & Context Discovery\n(Semantic Search · Tags · Skills)"]

        subgraph Workflow["③ Agent Workflow Orchestration"]
            Orch["Orchestrator Agent"]
            Workers["Worker Agents"]
            Orch -->|"delegate tasks"| Workers
        end

        subgraph Security["④ Security & Access Control"]
            ACL["Fine-Grained ACL\n(Scope · Role · Tool-level)"]
            AuthSrv["Auth Server\n(OAuth 2.0 / JWT)"]
        end

        MCPServers["⑤ MCP Servers\n& Enterprise Tools"]
    end

    subgraph External["Integrations"]
        IdP["Identity Provider\n(Keycloak · Cognito · Entra ID)"]
        OTEL["⑥ Observability\n(OpenTelemetry · Prometheus\nGrafana · Jaeger)"]
    end

    Copilot -->|"MCP / SSE / Streamable HTTP"| Discovery
    A2AAgent -->|"A2A / JSON-RPC 2.0 / HTTP+JSON"| Discovery

    Discovery --> Workflow
    Discovery --> Security

    Security -->|"verify token"| AuthSrv
    AuthSrv <-->|"authenticate & authorize"| IdP
    AuthSrv -->|"enforce permissions"| ACL

    Workflow --> MCPServers
    ACL --> MCPServers

    MCPServers -.->|"traces · metrics · logs"| OTEL

    classDef entry fill:#e3f2fd,stroke:#1565c0,stroke-width:2px
    classDef discovery fill:#e8eaf6,stroke:#283593,stroke-width:2px
    classDef workflow fill:#f3e5f5,stroke:#6a1b9a,stroke-width:2px
    classDef security fill:#fff8e1,stroke:#e65100,stroke-width:2px
    classDef mcp fill:#fce4ec,stroke:#b71c1c,stroke-width:2px
    classDef idp fill:#e8f5e9,stroke:#2e7d32,stroke-width:2px
    classDef otel fill:#f1f8e9,stroke:#33691e,stroke-width:2px

    class Copilot,A2AAgent entry
    class Discovery discovery
    class Orch,Workers workflow
    class ACL,AuthSrv security
    class MCPServers mcp
    class IdP idp
    class OTEL otel

Built by ASCENDING Inc

Jarvis Registry is developed and maintained by ASCENDING Inc. For more information about Jarvis AI and our broader AI platform: