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. 41 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 7 · avg 4 · -3% w/w
a month agotoday
41
Installs / week
npm · gitwhy-mcp
0
Stars
0 open issues
28 Mar 2026
Last commit
no releases in 90 days
MIT
License
language unknown

What the code does

We have not read this server's code yet, 4 d ago · rules 995398eba69f

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": {
      "command": "npx",
      "args": [
        "-y",
        "gitwhy-mcp"
      ]
    }
  }
}
~/.codex/config.toml
[mcp_servers.gitwhy]
command = "npx"
args = ["-y", "gitwhy-mcp"]
.cursor/mcp.json
{
  "mcpServers": {
    "gitwhy": {
      "command": "npx",
      "args": [
        "-y",
        "gitwhy-mcp"
      ]
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "gitwhy": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "gitwhy-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: GITWHY_API_KEY (GitWhy API key for cloud sync, publish, and PR comment features. Not required for local-only context saving).

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.

224 installs/wk local only
Clawhub
by maxz712

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

34 installs/wk local only
ContextStream MCP Server
by contextstreamio

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

3 749 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.

671 installs/wk local only
OpenGrok MCP Server
by icyhot09

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

167 installs/wk local only
WingFoil
by wingfoil

WingFoil — the repo-native intent layer for AI-native software engineering

1 127 installs/wk local only
Codeweaver
by knitli

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

83 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 41 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 in the form 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 41 times in the last week. Week over week that is -3%. 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?
Yes — it is published under the MIT licence and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.