Git Enhanced MCP server

MCP Git Enhanced

MCP Git Enhanced is a Model Context Protocol server that helps AI coding assistants inspect repository state for day-to-day open-source maintenance.

It gives maintainers structured Git context for code review, commit analysis, branch comparison, and release preparation without asking the assistant to run broad shell commands.

Why Maintainers Use It

Open-source maintainers spend a lot of time answering the same repository questions before they can review or merge work:

• What changed in this branch?
• Which commits matter for the release notes?
• Is this branch behind the base branch?
• What is staged, unstaged, or untracked?
• Which merged or stale branches need cleanup?

This server exposes those workflows as focused MCP tools so assistants can help with PR review, issue triage, release management, and repository hygiene.

Available Tools

Installation

From Source

git clone https://github.com/davidweb3-ctrl/mcp-git-enhanced.git
cd mcp-git-enhanced
npm install
npm run build

Claude Code Configuration

Use the built server from this repository:

{
  "mcpServers": {
    "git-enhanced": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-git-enhanced/dist/index.js"]
    }
  }
}

Future npm Install

The package is published as @davidweb3-ctrl/mcp-git-enhanced:

npm install -g @davidweb3-ctrl/mcp-git-enhanced

After publication, clients can use:

{
  "mcpServers": {
    "git-enhanced": {
      "command": "npx",
      "args": ["@davidweb3-ctrl/mcp-git-enhanced"]
    }
  }
}

Example Workflows

PR Review

Use git_diff to compare this branch with master and summarize the risky files.
Use git_log to list commits since the last release.
Use git_commit_analyze on the largest commit before I review it.

Issue Triage

Use git_log to find recent commits touching src/tools.ts.
Use git_status to check whether the local reproduction has uncommitted changes.

Release Management

Use git_branch compare against master to prepare release notes.
Use git_log with --stat style output to identify user-visible changes.
Use git_branch suggest_cleanup after the release branch is merged.

Tool Examples

git_diff

{
  "repoPath": "/absolute/path/to/repo",
  "target": "HEAD~5",
  "source": "HEAD~10",
  "filePath": "src/",
  "staged": false
}

git_log

{
  "repoPath": "/absolute/path/to/repo",
  "maxCount": 20,
  "author": "Maintainer Name",
  "since": "1 week ago",
  "stat": true
}

git_branch

{
  "repoPath": "/absolute/path/to/repo",
  "action": "list",
  "includeRemote": true
}

{
  "repoPath": "/absolute/path/to/repo",
  "action": "compare",
  "branchName": "feature/pr-review-summary",
  "baseBranch": "master"
}

git_status

{
  "repoPath": "/absolute/path/to/repo",
  "short": false
}

gitcommitanalyze

{
  "repoPath": "/absolute/path/to/repo",
  "commitHash": "abc123"
}

Security Model

Shortened. The full README is on GitHub.