mcpbeat Sign in

GitWhy — The Context Layer for Git MCP Server

by gitwhy-cli Your server? Claim it
local only

GitWhy — The Context Layer for Git runs on your own machine — the client starts it, so there is no endpoint to ping. 29 installs a week from npm. Last commit 28 Mar 2026.

The shared AI context engine for git — save, search, and share the reasoning behind code changes.

Installs per day peak 23 · avg 5 · +27% w/w
a month agotoday
29
Installs / week
npm · gitwhy-mcp
0
Stars
0 open issues
28 Mar 2026
Last commit
0 releases in 90 days
License
language unknown

What the code does

We have not read this server's code yet, 19 h ago · rules 3dff92dd89df

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Runs a command on install [пакет] package.json:1
postinstall: node install.js
File ships in the package but is absent from the source [пакет] install.js:1, [пакет] run.js:1
этот файл ставится пользователю, но в репозитории его нет
Builds a file path from a variable [пакет] install.js:151, [пакет] run.js:20
  const binaryPath = path.join(destDir, binaryName);
Runs an external command [пакет] run.js:28
    const systemPath = execFileSync(cmd, [binaryName], {

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add gitwhy -- npx -y gitwhy-mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "gitwhy": {
      "args": [
        "-y",
        "gitwhy-mcp"
      ],
      "command": "npx"
    }
  }
}
~/.codex/config.toml
[mcp_servers.gitwhy]
command = "npx"
args = ["-y", "gitwhy-mcp"]
.cursor/mcp.json
{
  "mcpServers": {
    "gitwhy": {
      "args": [
        "-y",
        "gitwhy-mcp"
      ],
      "command": "npx"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "gitwhy": {
      "args": [
        "-y",
        "gitwhy-mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: GITWHY_API_KEY (GitWhy API key for cloud sync, publish, and PR comment features. Not required for local-only context saving.). The author declared them in the registry entry; get the values from the project itself.

Alternatives to GitWhy — The Context Layer for Git

same job, measured the same way
Code Context Engine
by ai-elara

Index your codebase. AI searches instead of re-reading files. 94% token savings.

290 installs/wk local only
Clawhub
by maxz712

Git hosting for AI agents: repos, changes, focused diffs, reviews, issues, code search.

17 installs/wk local only
ContextStream MCP Server
by contextstreamio

ContextStream MCP server for code context, memory, search, and AI tools.

1 106 installs/wk local only
Agent Memory MCP
by ipiton

Memory, docs, and repo context layer for engineering agents.

local only
Vexor
by scarletkc

A semantic search engine for files and code.

842 installs/wk local only
OpenGrok MCP Server
by icyhot09

MCP server bridging OpenGrok search engine with AI for instant context across massive codebases.

362 installs/wk local only
Codeweaver
by knitli

Semantic code search built for AI agents. Hybrid, AST-aware, context for 166 languages.

142 installs/wk local only
Git Archaeologist
by engrmaziz

Trace code history, commit reasoning, and PR context directly from Git logs.

25 installs/wk local only

GitWhy — The Context Layer for Git — questions

Answers built from our own checks of this server.

Why is there no uptime for GitWhy — The Context Layer for Git?
GitWhy — The Context Layer for Git runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package gitwhy-mcp was installed 29 times last week.
How do I connect GitWhy — The Context Layer for Git?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It runs locally, so the command pulls gitwhy-mcp straight from npm; nothing to host, nothing to sign up for.
How many people use GitWhy — The Context Layer for Git?
The npm package gitwhy-mcp was installed 29 times in the last week. Week over week that is +27%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is GitWhy — The Context Layer for Git open source?
We cannot say either way: 0 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.