GitWhy — The Context Layer for Git
io.github.gitwhy-cli/gitwhy
The shared AI context engine for git — save, search, and share the reasoning behind code changes.
Description as published in the official MCP registry.
What we measured
| Endpoint | None listed (runs locally) | registry |
|---|---|---|
| GitHub stars | 0 | github.com/gitwhy-cli/gitwhy |
| Last push | 2026-03-28 | GitHub API |
| Registry version | 0.7.9 · active · updated 2026-04-01 | registry |
| Package | npm: gitwhy-mcp | registry |
Signed reports
No signed reports yet. A report carries a signed decision record from the reporter's gate, so it shows a real call went through, not just an opinion. How to file one.
Connect
npx -y gitwhy-mcpCommands are built from the registry entry. Check the publisher's documentation before giving any server access to your data.
Related servers
- Context Awesome MCP server for accessing curated awesome list documentation
- ClariLayer Individual-analyst context layer: recall, remember, and reconcile your data and…
- Synapse Layer — Trust Infrastructure for AI Agents MCP-native Trust Infrastructure for AI Agents. Persistent encrypted memory with Trust…
- FreshContext Context integrity for AI agents: evaluate freshness, confidence, provenance, and decision…
- ContextStream Persistent memory and cross-session learning for AI coding assistants (hosted remote MCP).
- ContextStream MCP Server Project memory, semantic code search, and grounded agent context.
Badge for your README
Shows the result of our latest check and links back to this page.
[](https://openforallofus.com/tools/io.github.gitwhy-cli/gitwhy)Agents can read this page as data: MCP endpoint https://openforallofus.com/api/mcp, tool get_tool with name io.github.gitwhy-cli/gitwhy.