Ext Ops Panel
Open dashboard
Comparison

keep-the-why vs Git

keep-the-why is a plugin bundle for AI coding tools published by oliver-zehentleitner. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). Git is an MCP server published by Abhishekkumar2021. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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
Marketplacekeep-the-whyGit
Copilot CLI: github/awesome-copilot Listed
Version: 0.20.2
Forks (GitHub): 13
Stars (GitHub): 231
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.0
Downloads/month (npm): 183
Downloads/week (npm): 32
Forks (GitHub): 0
Stars (GitHub): 1
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

keep-the-why vs Git
Factkeep-the-whyGit
Marketplaces that list it11
Stars (GitHub) (differs)231 (better)1 (worse)
Forks (GitHub) (differs)13 (better)0 (worse)
Last release (differs)2026-10-14Not published
Where it runs (differs)Installs as a plugin bundleOn your machine (@abhishekmcp/git)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 0
Parts of the bundle (differs)2Not a bundle
LicenceMITMIT
Repository (differs)github.com/oliver-zehentleitner/keep-the-whygithub.com/abhishekkumar2021/mcp-suite
Changes in the last 7 days22
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

keep-the-why

In its own words, on Copilot CLI: github/awesome-copilot:

Preserves or recovers the reasoning behind a codebase — architectural decisions, rejected alternatives, workarounds, incident learnings, operational constraints, and historical context the code itself cannot explain.

Git

In its own words, on Official MCP Registry:

Local Git via MCP: status, log, diff, file history, branches, and gated stage/commit. Pure-JS.

How to run each

keep-the-why

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

Git As a local MCP server: npm package

Claude Code
claude mcp add --env "GIT_ROOTS=<YOUR_GIT_ROOTS>" --transport stdio git -- npx -y @abhishekmcp/git

Requires: GIT_ROOTS

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 keep-the-why publish no settings it asks for, so we do not compare settings.

What it can do: keep-the-why · What it can do: Git · Compare two other plugins

Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. 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