Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

git-a2a

by neprelversion 1.7.1i★ –iRuns on your computer
Registry nameio.github.neprel/git-a2a

Install

Overview

Description from the maker (original English)

Git module dependencies and owning-agent routing for coding agents

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Developer tools

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Download the maker’s .mcpb file

The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.

Run this in your terminal

claude mcp add git-a2a -- npx -y git-a2a mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "git-a2a": {
      "command": "npx",
      "args": [
        "-y",
        "git-a2a",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "git-a2a": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "git-a2a",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account neprel, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Developer toolsi

  • More stars than 0% of the other 1386 servers in this category
  • Published to the registry more recently than 45% of the other 1386 servers in this category
  • Basic checks equal to or better than 100% of the other 1386 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is git-a2a safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.7.1) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker, MCPB on your computer.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

by github

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

Computer or cloud★ 34,245MITUpdated 3 days ago
Install

Desktop Commander

by wonderwhy-er

MCP server for terminal commands, file operations, and process management

Runs on your computer★ 10,225MITUpdated 15 days ago
Install

Cloudflare MCP

by cloudflare

Cloudflare MCP servers

Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

git-a2a

Connect a Git component together with the agent responsible for it.

git-a2a is a cross-platform component dependency manager. A component repository publishes code, one A2A Agent Card reference for its owner, and optionally a readable surface such as API documentation, examples, or source. A consumer connects the code through its own platform's adapter and records the exact commit, adapter, and package-manager variant.

git-a2a does not send messages, manage tasks, run agents, or host Agent Cards. Use the usable Agent Card reference shown by git a2a whose NAME with an external A2A client: an HTTPS URL or a local copy of a repository-relative card from the applied commit.

Quick start

Run the binary directly as git-a2a, or install it on PATH and use Git's equivalent git a2a form:

git a2a init

git a2a add https://github.com/acme/lib-utils.git --name lib-utils git a2a list git a2a whose lib-utils git a2a pull lib-utils git a2a remove lib-utils

Version 2.1.0 introduces whose NAME and removes the positional argument from list. Scripts using list NAME --json must use list --json and select the alias from the array.

There are exactly six domain commands:

CommandResult
initCreates a minimal schema 2 a2amodule.yml without overwriting an existing manifest.
add SOURCEResolves one commit, chooses applicable adapters, connects the component, and records its owner and surface.
pull [NAME]Updates one or every dependency through the adapters and variants chosen by add; with no dependencies it reports No dependencies. and succeeds without mutation.
remove NAMERemoves only the selected dependency's owned integration and local materialization.
listReports every direct dependency, commit, adapter, Agent Card, surface, and local problem; --json returns the existing array format.
whose NAMEReports one dependency's responsible agent, usable Agent Card reference, optional local surface, and recoverable metadata problems; --json returns one object.

pull is adapter lifecycle, not a wrapper around git pull. All bindings of a polyglot component use the same resolved commit. Adapter and manager selection is durable: a later change to PATH or consumer marker files cannot silently switch it.

End-to-end demo

The ACME app walkthrough demonstrates the complete loop: connect a component, discover its responsible agent, send a request through A2A, let the owner change the library, run git-a2a pull, and observe the new result. The app repository and library repository must be cloned next to each other. Docker with Compose is the only runtime requirement:

git clone https://github.com/neprel/git-a2a-demo-acme-lib.git

git clone https://github.com/neprel/git-a2a-demo-acme-app.git cd git-a2a-demo-acme-app ./demo/run.sh

Short npm-only profile

DEMO_PROFILE=npm ./demo/run.sh

The demo uses deterministic agents without LLM API keys, real A2A transport, the published git-a2a 2.0.0, and temporary local Git remotes. The separate demo client performs A2A communication; git-a2a manages dependency code and metadata. The agents exist only for the local run and are not permanently available public services. See the verified transcript for the recorded full-profile result.

Component contract

a2amodule.yml uses schema 2:

schema: 2

component: id: lib-utils description: Shared parsing and validation utilities. repository: https://github.com/acme/lib-utils.git exports:

  • adapter: npm name: "@acme/lib-utils"
  • adapter: pypi name: acme-lib-utils surface: docs/public

agent: name: lib-utils-owner card: https://agents.acme.example/lib-utils/.well-known/agent-card.json

The Agent Card remains the authority for the agent's interfaces, skills, and authentication. The manifest deliberately does not duplicate them. init may create an incomplete local manifest without agent; a repository consumed by add or pull must declare agent.card.

The optional component.surface is published data from the same applied commit and is materialized under .git-a2a/surfaces/NAME. If no surface is declared, no repository content is implicitly published. Surface is not an installation mechanism and is not a submodule.

See the manifest reference, authoring guide, consumer guide, and schema 1 migration guide.

Adapter matrix

Every existing platform integration is retained. Native adapters apply dependencies through the platform's own manager, updating declarations, native locks, and installed or resolved state; build-system adapters compose with one submodule checkout rather than copying source into a second tree.

ModeAdapters
Native Git dependencynpm (npm, Yarn, pnpm, Bun), Python (uv, Poetry, PDM, PEP 621/pip), Go, Cargo, SwiftPM, Pub, Bundler, Composer, Mix, Cabal/Stack, Zig, Clojure, Nix
Submodule + build integrationCMake, Gradle, MSBuild, Maven, Meson
Submodule onlyFallback when no integration applies or the native manager cannot represent the source

Git submodule is an ordinary adapter with the same add/pull/remove/inspect lifecycle. Native lockfiles remain owned by their package managers. See Works with for the detailed matrix and boundaries.

Installation

These existing installation channels are preserved. Commands track the latest stable release; pin a version in CI.

ChannelCommand
Gogo install github.com/neprel/git-a2a/v2/cmd/git-a2a@latest
Go zero-installgo run github.com/neprel/git-a2a/v2/cmd/git-a2a@latest --version
macOS/Linux installer`curl -fsSL https://git-a2a.com/install.sh \bash`
Windows installer`irm https://git-a2a.com/install.ps1 \iex`
Homebrewbrew install neprel/tap/git-a2a
Scoopscoop bucket add git-a2a https://github.com/neprel/scoop-bucket; scoop install git-a2a
npmnpx git-a2a@latest --version
PyPI with uvuvx git-a2a --version
PyPI with pipxpipx run git-a2a --version
Containerdocker run --pull=always --rm ghcr.io/neprel/git-a2a:latest --version
Nix flakenix run github:neprel/git-a2a -- --version

Linux .deb, .rpm, and .apk packages are attached to GitHub Releases. Release archives cover Darwin, Linux, and Windows on amd64/arm64 and include checksums and SBOMs. The standalone installers verify checksums and support version pinning, destination selection, and dry-run. Package-manager installs are updated with that package manager; the binary has no self-updater.

Maintainer and provenance details are in the release guide.

Documentation

  • CLI reference
  • Manifest reference
  • Authoring a component
  • Consuming components
  • Agents and external A2A clients
  • Supported adapters
  • Migrating from schema 1
  • FAQ
  • Release and installation maintenance

The portable Agent Skill teaches a coding agent this six-command workflow. It does not configure an MCP server or agent harness.

Specification as source

Repository decisions and invariants live in .hint files beside the artifacts they govern. hint returns the knowledge governing a path, and hint check validates the linked research records. The repository and CI use HINT 2.0.1. See HINT for the tool and format.

License: MIT.

Ask PopNx