
Mcp Git Enhanced
io.github.davidweb3-ctrlPublished by GitHub account davidweb3-ctrlv1.0.0Updated Oct 24, 2026
Enhanced Git MCP Server - Code review, commit analysis, and branch management
Overview
A local MCP server that gives AI coding assistants structured, read-oriented Git context for code review, commit analysis and branch management.
- What you can do
- Analyze diffs across working tree, staged changes, branches, commits or specific paths
- Review commit history filtered by author, date range, branch, path and stats
- List branches, compare a branch against its base, or suggest cleanup candidates
- Summarize staged, unstaged and untracked repository state
- Inspect a single commit with metadata, changed files, statistics and diff output
- When to use it
- Useful when an assistant helps with pull request review, issue triage, release notes or repository hygiene and needs repository facts without running broad shell commands. Best suited to local repositories you or your team maintain.
- Requirements
- Runs as a local stdio process; Node.js 18.0.0 or newer and Git installed and available in PATH. Each tool call takes an absolute repoPath pointing to a Git repository. No accounts, API keys or environment variables are declared.
Installation
In SourceWeft
- Open Mcp Git Enhanced in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
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
Claude Code Configuration
Use the built server from this repository:
Future npm Install
The package is published as @davidweb3-ctrl/mcp-git-enhanced:
After publication, clients can use:
Example Workflows
PR Review
Issue Triage
Release Management
Tool Examples
git_diff
git_log
git_branch
git_status
git_commit_analyze
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
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
Source: README.md at commit 6dda5c1
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts