gitwhy-mcp
GitWhy MCP Server
The shared AI context engine for git — save, search, and share the reasoning behind code changes.
GitWhy captures the why behind every commit: reasoning, decisions, and trade-offs. This MCP server makes GitWhy's tools available to AI coding agents like Claude, Cursor, Windsurf, and VS Code Copilot.
Install
npm (recommended for MCP clients)
npm install -g gitwhy-mcpHomebrew (macOS/Linux)
brew install gitwhy-cli/tap/git-whyScoop (Windows)
scoop bucket add gitwhy https://github.com/quanng28/gitwhy-scoop-bucket
scoop install git-whyRelated MCP server: lore-mcp
MCP Configuration
Claude Desktop / Claude Code
Add to your MCP config (~/.claude/settings.json or Claude Desktop settings):
{
"mcpServers": {
"gitwhy": {
"command": "gitwhy-mcp",
"args": []
}
}
}Cursor
Add to .cursor/mcp.json:
{
"mcpServers": {
"gitwhy": {
"command": "npx",
"args": ["-y", "gitwhy-mcp"]
}
}
}VS Code
Add to .vscode/mcp.json:
{
"servers": {
"gitwhy": {
"command": "npx",
"args": ["-y", "gitwhy-mcp"]
}
}
}Tools
Tool | Description |
| Save development context (reasoning, decisions, trade-offs) for the current session |
| Retrieve a saved context by its ID |
| Search saved contexts by keyword or natural language query |
| Browse saved contexts by domain/topic hierarchy |
| Check setup state, pending commits, and sync status |
| Upload local contexts to the cloud (private) |
| Share synced contexts with your team |
| Post context summary as a GitHub PR comment |
Authentication
For cloud features (sync, publish, PR comments), you need a GitWhy API key:
Sign up at app.gitwhy.dev
Get your API key at app.gitwhy.dev/dashboard/api-keys
For local CLI: run
git why setupto authenticateFor remote (Smithery/Glama): paste your API key when prompted
Links
License
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
Alicense-qualityCmaintenanceProvides persistent memory for AI coding assistants, storing and retrieving architectural decisions, patterns, and solutions across sessions using semantic search, while also offering git integration for commit messages and code expertise mapping.Last updatedMIT- AlicenseAqualityCmaintenanceArchitectural memory layer for AI coding. Automatically extracts decisions, detects security gaps, and analyzes git history from your codebase in one command.Last updated3232MIT
- AlicenseAqualityBmaintenanceChange tracking for AI-era codebases. AI agents call it to log structured change events (entity + diff + reasoning) before the session ends, then query history with diff, blame, history, changeset, and search. Captures the intent that would otherwise evaporate.Last updated817MIT
- AlicenseAqualityAmaintenanceLocal-first memory layer for AI coding agents — captures issues, attempts, fixes, and decisions, and warns at git commit before you repeat a mistake.Last updated15182MIT
Related MCP Connectors
Universal memory for AI agents and tools. Save, organize and search context anywhere.
Secure, user-owned long-term memory for AI agents over OAuth-protected remote MCP. Save, search, recall, update, and govern preferences, project context, decisions, and task state across ChatGPT, Claude, Copilot, IDEs, and CLIs.
Give your AI agent a persistent map of your project's structure, dependencies, and bugs.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/gitwhy-cli/gitwhy-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server