About git-enhanced
git-enhanced is an MCP server for maintainers and coding assistants to inspect local Git repositories. Its focused, read-oriented tools cover reviews, commit analysis, branch comparisons, and repository status without exposing destructive Git operations.
Key features
- 01Inspect working-tree and branch diffs
- 02Filter commit history
- 03Compare branches and find cleanup candidates
- 04Review staged, unstaged, and untracked files
- 05Analyze commit metadata and changes
Use cases
- 01Review changes in a pull request
- 02Find commits relevant to issue triage
- 03Prepare release notes from branch history
- 04Check repository state before maintenance
MCP support
Exposes focused Git inspection tools to MCP clients, including diff, log, branch, status, and commit analysis. It validates repository paths and does not offer destructive operations such as reset or push.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y @davidweb3-ctrl/mcp-git-enhancedYOUR_API_KEYSecretYour API key for the serviceLocal servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
5Saved tool list · updated 2w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| source | string | No | Source to diff from (commit hash, branch name). If omitted with target, diffs target against working directory. |
| staged | boolean | No | Show staged changes only (git diff --cached) |
| target | string | No | Target to diff against (commit hash, branch name, or 'HEAD'). If omitted, shows uncommitted changes. |
| filePath | string | No | Specific file or directory path to diff (relative to repo root) |
| repoPath | string | Yes | Absolute path to the git repository |
Details
From the project READMEMCP 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
| Tool | Purpose |
|---|---|
git_diff | Analyze working tree, staged, branch, commit, or path-specific diffs. |
git_log | Review commit history with filters for author, date range, branch, path, and stats. |
git_branch | List branches, compare a branch to its base, or suggest cleanup candidates. |
git_status | Summarize staged, unstaged, and untracked repository state. |
git_commit_analyze | Inspect one commit with metadata, changed files, statistics, and diff output. |
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
}
git_commit_analyze
{
"repoPath": "/absolute/path/to/repo",
"commitHash": "abc123"
}
Security Model
MCP Git Enhanced is designed as a read-oriented repository inspection server.
- It runs fixed
gitsubcommands throughspawnSyncwithout shell interpolation. - It does not expose destructive branch deletion, reset, checkout, rebase, push, or force-push tools.
- It validates that
repoPathpoints to a Git repository before executing tool handlers. - It is intended for local repositories controlled by the user or maintainer.
See SECURITY.md for reporting and supported-version details.
Development
npm install
npm run build
npm test
npm run lint
npm run format:check
Project Files
- CONTRIBUTING.md: development setup and contribution process.
- SECURITY.md: vulnerability reporting and trust boundaries.
- ROADMAP.md: planned maintainer workflows and release direction.
- CHANGELOG.md: release notes.
- docs/CODEX_FOR_OSS.md: Codex for Open Source maintenance plan.
Requirements
- Node.js >= 18.0.0
- Git installed and available in
PATH
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.