GitWhy — The Context Layer for Git MCP Server
API key requiredThe shared AI context engine for git — save, search, and share the reasoning behind code changes.
To add GitWhy — The Context Layer for Git to Claude, run the install command below or copy the ready-made config for Claude Code, Claude Desktop, Cursor and VS Code further down. Restart your client after adding it and its tools show up in your next conversation. It needs one environment variable, listed below.
Install
npx -y gitwhy-mcp@0.7.9Environment variables
GITWHY_API_KEYSet in your MCP configInstall with your client
claude mcp add gitwhy-the-context-layer-for-git --env GITWHY_API_KEY=<YOUR_GITWHY_API_KEY> -- npx -y gitwhy-mcp@0.7.9
Run this in a terminal to add the server to Claude Code.
What this does
GitWhy — The Context Layer for Git exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.
Requirements
This server needs the following environment variables to be set before it can run:
GITWHY_API_KEY
Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).
Frequently asked questions
How do I install GitWhy — The Context Layer for Git?
Run the Claude Code command in the install section to add GitWhy — The Context Layer for Git to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.
Which clients work with GitWhy — The Context Layer for Git?
This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to GitWhy — The Context Layer for Git as well.
Does GitWhy — The Context Layer for Git need an API key?
Yes. Before it can run, set this environment variable: GITWHY_API_KEY. They go in the env block of your MCP config.
Imported from the Official MCP Registry. The details above come from the registry entry; the maker can claim this listing to correct them, add docs, and see its traffic.
Is this your MCP server?
Claim this listing to see its traffic, fix details yourself, and skip the review queue on future updates.
Add this badge to your README
Show visitors this server is listed in the ClaudeRules directory. The badge links straight to this listing.
[](https://clauderules.net/mcp/io-github-gitwhy-cli-gitwhy)<a href="https://clauderules.net/mcp/io-github-gitwhy-cli-gitwhy" target="_blank" rel="noopener noreferrer"><img src="https://clauderules.net/api/badge/io-github-gitwhy-cli-gitwhy" alt="Listed on clauderules.net" /></a>More Search MCP servers
GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
Serena MCP: the IDE for your agent
A powerful toolkit for coding, providing semantic retrieval and editing capabilities.
mediar-ai/screenpipe
🎖️ 🦀 🏠 🍎 Local-first system capturing screen/audio with timestamped indexing, SQL/embedding storage, semantic search, LLM-powered history analysis, and event-triggered actions - enables building c
MCP Toolbox for Databases
MCP Toolbox for Databases enables your agent to connect to your database.