Ext Ops Panel
Open dashboard
Comparison

io.github.Alejandro-M-P/git-courer vs GitWhy — The Context Layer for Git

io.github.Alejandro-M-P/git-courer is an MCP server published by Alejandro-M-P. Marketplaces we read that list it: 1 (Official MCP Registry). GitWhy — The Context Layer for Git is an MCP server published by gitwhy-cli. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceio.github.Alejandro-M-P/git-courerGitWhy — The Context Layer for Git
Official MCP Registry Listed
Version: 2.0.4
Forks (GitHub): 5
Stars (GitHub): 43
Not marked · First seen
Listed
Version: 0.7.9
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

io.github.Alejandro-M-P/git-courer vs GitWhy — The Context Layer for Git
Factio.github.Alejandro-M-P/git-courerGitWhy — The Context Layer for Git
Marketplaces that list it11
Stars (GitHub) (differs)43 (better)0 (worse)
Forks (GitHub) (differs)5 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Not statedOn your machine (gitwhy-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/alejandro-m-p/git-courergithub.com/gitwhy-cli/gitwhy
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

io.github.Alejandro-M-P/git-courer

In its own words, on Official MCP Registry:

Full git MCP server for LLM agents — 17 tools, AST annotator, auto-backups, real plumbing.

GitWhy — The Context Layer for Git

In its own words, on Official MCP Registry:

The shared AI context engine for git — save, search, and share the reasoning behind code changes.

How to run each

io.github.Alejandro-M-P/git-courer

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

GitWhy — The Context Layer for Git As a local MCP server: npm package

Claude Code
claude mcp add --env "GITWHY_API_KEY=<YOUR_GITWHY_API_KEY>" --transport stdio gitwhy -- npx -y gitwhy-mcp

Requires: GITWHY_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of io.github.Alejandro-M-P/git-courer publish no settings it asks for, so we do not compare settings.

What it can do: io.github.Alejandro-M-P/git-courer · What it can do: GitWhy — The Context Layer for Git · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built