Git Why
Finds the Git commits that explain why code is the way it is: semantic and full-text history search.
Open the source (opens github.com) https://github.com/alliecatowo/git-why
Before you use it
- Runs on your computer with your permissions. Read what it can do before connecting it to an agent.
What it is
MCP servers from io.github.alliecatowo.
The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.
How to get it
npm package (stdio)
@alliecatowo/git-why@0.2.0
From the server's entry in the official MCP Registry
Related
-
WhyKit
MCP serversRead-only decisions and evidence from a Git vault, and which decisions a code change touches.
whykit@0.5.1 -
whygit
MCP serversRead-only Git explainer: what state a repo is in, what an error means, and the exact fix.
whygit@0.1.2 -
gitpro
MCP serversRead-only checks of which git name, email and SSH key a repository uses, and why.
gitpro@0.4.6 -
MCP reference servers
MCP serversSmall example servers from the MCP project (filesystem, git, fetch, memory and more) that show how MCP works.
-
ontology-atlas
MCP serversUnderstand what your codebase builds, why it is structured that way, and what a change could affect. One shared Markdown ontology for humans and coding agents—visualized for people, accessible to agents through MCP, and reviewed with Git. Local-first. Open source.
git clone https://github.com/wlsdks/ontology-atlas.git -
why3-mcp
MCP serversWhy3 MCP: 20 real tools to read, check, lint, scaffold, build and run Why3 code.
@mrfentmen/why3-mcp@1.0.0