Set it up
- 1
Turn on Git in your AI
In Claude: open Settings → Connectors and add Git. In ChatGPT: Settings → Apps & Connectors.
- 2
Add it to your app once
Copy the short config below into your app. It just tells your AI where to find Git.
- 3
Just ask
Tell it what you want in plain words — no special commands.
For example, say
“Show me the last 10 commits in this repo and summarize each one in a sentence”
Need the exact config? Show it +
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.
Quick skills
Copy one, paste it to your AI, watch it work.
Recent Changes Summary
“Show me what changed in the last 10 commits and summarize each change”
Blame Investigation
“Who last modified the authenticate function in auth.ts, and what was the context?”
Branch Comparison
“Compare main and the feature/payments branch — summarize what the feature branch adds”
In the wild
“fixes included Playwright CLI changes and Vercel routing for serverless/SPA apps and manually needing to step in to fix Git MCP server configuration”
Good to know
- · 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
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
About
Imagine telling your AI: 'Show me what changed in this repo today' or 'Find the commit that introduced this bug' — and it reads your local git history directly. This server lets your AI query git repositories: log, diff, show, blame, and branch info through conversation.
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.
Workflows That Use Git MCP
Works With
Also Consider
FAQ
What does Git MCP do? +
Imagine telling your AI: 'Show me what changed in this repo today' or 'Find the commit that introduced this bug' — and it reads your local git history directly. This server lets your AI query git repositories: log, diff, show, blame, and branch info through conversation.
Do I need to know how to code? +
No. Turn it on in your AI's settings and ask in plain English — no terminal, no coding.
When should I use Git MCP? +
Reach for it when you need to: 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 should I avoid Git MCP? +
Skip it when: 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.
How do I install Git MCP? +
In Claude Code, run: claude mcp add git -- uvx mcp-server-git --repository /path/to/your/repo. Copy-paste configs for Claude Desktop, Cursor, and Windsurf are at the top of this page.
