Skip to content
Agentmart
Submit a tool

Git Why

Finds the Git commits that explain why code is the way it is: semantic and full-text history search.

Connector by alliecatowo · GitHub account verified by the MCP Registry

IndexedApache-2.0Local (stdio)
Write a review

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/alliecatowo-git-why

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Finds the Git commits that explain why code is the way it is: semantic and full-text history search.

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools
2 read · 0 write · 0 deleteRead-only
Secrets
None asked for
Install scripts
Not scanned yet
Runs as
Node.js package

Tools by what they do 2

Read from the source code; the running server may list different tools.

Read 2 · Look things up without changing anything.

  • git_why_search
  • git_why_status

Files it touches

  • Any path the agent passes to its tools

Tools (2)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • git_why_search

    Find the commits that explain WHY code is the way it is: the rationale behind a design, whether an approach was already tried and reverted, what a past incident was, or who established an area. USE THIS when you cannot name the exact symbol or string to search for. On questions where keyword search fails, it scores ~18x `git log --grep`. DO NOT USE THIS when you already know the identifier. `git log -S<symbol>` is measurably better for that (Hit@10 0.950 vs 0.350) -- if you can see the name in the code, run pickaxe search instead. For the CURRENT state of the code rather than its history, us…

  • git_why_status

    Report whether this repository's history index exists and is current. USE THIS when git_why_search returns an index error, or before searching a repository for the first time. The answer is actionable: if "state" is not "current", run `git why index --if-needed` in a shell -- it is idempotent and takes about 0.2s when there is nothing to do. An index is built once per repository and shared by all its worktrees. A first build on a large repository takes minutes, so do it deliberately rather than inside a loop.

Signals

Stars
0
Forks
0
Open issues
0
Weekly downloads
23
Last commit
Oct 23, 2026 (6 days ago)
Last release
Oct 4, 2026 (25 days ago)
Last package publish
Oct 4, 2026 (25 days ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name
io.github.alliecatowo/git-why
Version
0.2.0
Auth
No auth
Packages
npm @alliecatowo/git-why
License
Apache-2.0
Repository
github.com/alliecatowo/git-why
Website
alliecatowo.github.io/git-why/
First seen
Oct 24, 2026
Last checked
Oct 25, 2026
Source
Official MCP Registrygithub-graphql
Cite this page

Git Why MCP server. Agent Mart. https://agentmart.dev/connectors/alliecatowo-git-why (last updated 2026-10-25)