Git MCP
Official Git MCP server — read repository history, diffs, blame, and status through AI without leaving your conversation.
// Add to your client
{
"mcpServers": {
"git": {
"command": "uvx",
"args": ["mcp-server-git", "--repository", "/path/to/your/repo"]
}
}
}Paste into your client's MCP configuration file.
// Try it now
"Show me the last 10 commits in this repo and summarize each one in a sentence"
- ! The server reads whatever repo path you give it — double-check you're pointing at the right one
- ! Large histories can be slow to process — scope queries by path or time range
- ! Uncommitted changes aren't in git history — diff against working tree if needed
API key or simple config
// When to use
- You want AI to explain what changed recently in a repo
- You're investigating when or why a specific change was made
- You want to navigate git history conversationally instead of memorizing commands
- You're reviewing a branch and want AI-assisted diff summaries
// When NOT to use
- You need GitHub-specific features (issues, PRs) — use github-mcp
- You want to push or pull to remote repos — this is read-focused on local history
- You need to manipulate the working directory aggressively — stick with direct git commands
// Usage Scenarios
Recent Changes Summary
Get a natural-language summary of what landed recently.
Example prompt
"Show me what changed in the last 10 commits and summarize each change"
Blame Investigation
Find who wrote a specific line and when.
Example prompt
"Who last modified the authenticate function in auth.ts, and what was the context?"
Branch Comparison
Compare two branches and summarize differences.
Example prompt
"Compare main and the feature/payments branch — summarize what the feature branch adds"
// About
Plain English
Git is the system that records every change to a project's code over time — who edited what, when, and why. The history is incredibly useful when something breaks or when you're trying to understand why a piece of code looks the way it does. The catch is that pulling answers out of git usually means typing cryptic commands into a terminal. This server lets your AI assistant read that history for you. Ask 'what changed in this repo today,' 'who last edited the login function and what did they say in the commit message,' or 'find the change that broke this test' — and Claude looks through the git history and writes back a plain-English answer. It only reads, so there's no risk of breaking the repo. It's especially handy when you're new to a codebase and want to understand how it got to its current shape, when you're hunting down a regression, or when you want a quick summary of what shipped this week. The setup is easy: point it at a folder on your machine that contains a git repository.
The official Git MCP server provides AI assistants with read access to local Git repositories. Inspect commit history, view diffs, check blame, examine branches, and understand codebase evolution — all through natural language.
A fundamental tool for AI-assisted code review, debugging, and understanding unfamiliar codebases.
// Use Cases
- Understand commit history and code evolution
- Review diffs and understand what changed and why
- Investigate blame for specific lines of code
- Navigate large codebases through AI guidance
// Works With
// Also Consider
// Related Servers
Puppeteer MCP
Official Puppeteer browser automation server — let AI control a real browser for scraping, screenshots, and UI testing.
GitHub MCP
Official GitHub MCP server — manage repos, issues, PRs, and code search directly from your AI assistant.
Playwright MCP
Official Microsoft Playwright browser automation server — AI-powered cross-browser testing and web interaction.