SkillFoxx

Jarvis Registry MCP

A self-hosted MCP and A2A gateway with identity provider integration, access control and observability for enterprise agents

  • 3,935 ★ on the repository
  • Last commit
  • Apache-2.0
MCP serverOfficial

Broad access

Why this level

  • Controls agent access to internal corporate systems and data
  • Requires configuring an identity provider and stores its credentials
All reasons and checks

ascending-llc/jarvis-registryAuthor:ASCENDING Inc

Install

Manual install

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

Fill in .env with your identity provider credentials before starting.

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • Controls agent access to internal corporate systems and data
  • Requires configuring an identity provider and stores its credentials

This is third-party code. Review the repository files before installing.

What it does

Jarvis Registry gives you one secured entry point through which AI copilots like Cursor, Claude Desktop, GitHub Copilot and VS Code reach a company's internal tools over MCP via SSE or Streamable HTTP. It also supports registering and orchestrating autonomous agents over A2A, where an orchestrator agent coordinates worker agents through the same gateway. Access is built on OAuth 2.0 and OIDC with Keycloak, Amazon Cognito or Microsoft Entra ID integration, and an ACL engine grants permissions down to a specific tool. Semantic search over skill descriptions and tags helps agents find the right MCP server or A2A agent at runtime, alongside full request logging, OpenTelemetry tracing and Prometheus metrics.

Who it is for. For devops engineers and IT teams who need to give enterprise AI copilots governed access to internal systems.

Good fit when

  • You need one entry point for several AI copilots instead of separate integrations for each internal tool
  • You need role-based access control and a corporate identity provider instead of custom auth code
  • You need visibility into what requests agents make to internal systems and an audit trail

Not a fit when

  • You need a single local MCP server for personal use without an enterprise perimeter
  • You lack the resources to deploy and maintain an identity provider and the docker infrastructure

Example request

Deploy Jarvis Registry locally and connect Cursor to our internal MCP servers through it

MCP

Transport
http, sse
Authentication
OAuth

Environment variables

identity provider credentials required, secret
Connection details for Keycloak, Amazon Cognito or Microsoft Entra ID, set in .env before startup.

Limitations

Requires configuring an identity provider through environment variables in .env and a full docker compose stack; there is no one-command cloud launch. Separate deployment guides exist for Kubernetes on AWS, Azure and GCP.

How to disable. Stop the stack with docker compose --profile full down and remove the cloned repository.

FAQ

Do I have to use Keycloak?

No, the README lists Keycloak, Amazon Cognito and Microsoft Entra ID as supported OAuth 2.0 or OIDC provider options.

Can I deploy this in the cloud instead of locally?

Yes, the README links to separate guides for AWS EKS, Azure AKS and GCP GKE in addition to the local docker compose setup.

Discussion

No questions or reviews yet.

MCP servers

MCP Gateway Registry

mcp-gateway-registry

One registry and gateway for MCP servers, agents and skills: shared login, OAuth, audit, OpenTelemetry. Community project for Docker and cloud

MCP serverBroad access1K

Agentgateway

agentgateway

Official

A proxy for agentic traffic: routes and secures connections to MCP servers, LLMs, and other agents over A2A

MCP serverBroad access6.1K

An IBM gateway and registry that federates MCP servers, A2A agents and REST or gRPC APIs behind one endpoint with auth and observability

MCP serverBroad access4.8K
Official

A self-hosted gateway routes internal MCP tools, authenticates users and records requests for later review.

MCP serverBroad access587

AIHelms is an organizational MCP gateway that attributes calls to employee keys and tracks configured per-tool costs.

MCP serverBroad access1K

A secure MCP runtime through which an agent operates local machines, servers and containers

MCP serverBroad access1.3K

README in short

The README describes Jarvis Registry as an open-source MCP and A2A gateway with workflow orchestration from ASCENDING Inc, solving the problem of secure, governed AI agent access to internal tools. It lists an MCP reverse proxy over SSE or Streamable HTTP, integration with Cursor, Claude Desktop, GitHub Copilot and VS Code copilots, A2A agent registration and orchestration, identity management via OAuth or OIDC, tool-level ACLs, semantic skill search, and full audit trails with OpenTelemetry and Prometheus. Quick start is git clone, configure .env, uv sync, and docker compose --profile full up. Separate guides cover cloud deployment on AWS, Azure and GCP.

README badge

Report a problem