Git
Local Git operations: commit, diff, log, branch, and more.
What it does
Executes Git operations on local repositories: status, diff, log, commit, branch, checkout, merge, and more.
Why it matters
Developers need Git context to understand code history and changes. This MCP gives models that context directly, improving code assistance quality.
Best for
- Commit message generation
- Diff summarization
- Branch management
- Merge conflict help
- Code history exploration
Not ideal for
- GitHub API operations
- Remote repository management
- GitLab workflows
When to use it
When working with local Git repos and you want the AI to understand recent changes, commit history, or help write commit messages.
When not to use it
When you need GitHub API access (PRs, issues, remote repos) — use the GitHub MCP instead.
Key features
- Local Git operations
- Diff and status viewing
- Commit creation
- Branch management
- Log and history access
- Official Anthropic support
Frequently asked questions
What is the difference between Git MCP and GitHub MCP?
Git MCP operates on local repositories using git CLI operations. GitHub MCP uses the GitHub API for remote repos, issues, and PRs.
Can it create commits?
Yes. It can stage files and create commits with AI-generated or custom messages.
Install
$ uvx mcp-server-git --repository /path/to/repoScores
Details
- Pricing
- open source
- Setup time
- 2 min
- Complexity
- Low
Works with
Alternatives
- GitHub →
Full GitHub API access: repos, PRs, issues, and code search.
- Filesystem →
Read and write local files with configurable access controls.
More Git MCPs
Other tools in the same category worth evaluating.
Exploring Top MCPs for Git Workflows? See all Git MCPs →