Git MCP — Cas d'usage, Installer & Démo en direct

Pourquoi l'utiliser

Fonctionnalités clés

First-party — maintained in modelcontextprotocol/servers
Path-scoped — --repository /path limits blast radius to one repo
Read-only by default if you skip the write tools in your client config
Works offline — no network, no tokens, no rate limits

Démo en direct

Aperçu en pratique

git.replay ▶ prêt

0/0

Installer

Choisissez votre client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "git": {
      "command": "uvx",
      "args": [
        "mcp-server-git",
        "--repository",
        "/repo"
      ]
    }
  }
}

Ouvrez Claude Desktop → Settings → Developer → Edit Config. Redémarrez après avoir enregistré.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "git": {
      "command": "uvx",
      "args": [
        "mcp-server-git",
        "--repository",
        "/repo"
      ]
    }
  }
}

Cursor utilise le même schéma mcpServers que Claude Desktop. La config projet l'emporte sur la globale.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "git": {
      "command": "uvx",
      "args": [
        "mcp-server-git",
        "--repository",
        "/repo"
      ]
    }
  }
}

Cliquez sur l'icône MCP Servers dans la barre latérale Cline, puis "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "git": {
      "command": "uvx",
      "args": [
        "mcp-server-git",
        "--repository",
        "/repo"
      ]
    }
  }
}

Même format que Claude Desktop. Redémarrez Windsurf pour appliquer.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "git",
      "command": "uvx",
      "args": [
        "mcp-server-git",
        "--repository",
        "/repo"
      ]
    }
  ]
}

Continue utilise un tableau d'objets serveur plutôt qu'une map.

~/.config/zed/settings.json

{
  "context_servers": {
    "git": {
      "command": {
        "path": "uvx",
        "args": [
          "mcp-server-git",
          "--repository",
          "/repo"
        ]
      }
    }
  }
}

Ajoutez dans context_servers. Zed recharge à chaud à la sauvegarde.

claude mcp add git -- uvx mcp-server-git --repository /repo

Une seule ligne. Vérifiez avec claude mcp list. Supprimez avec claude mcp remove.

Cas d'usage

Usages concrets : Git

Have an agent review your staged changes before you commit

👤 Solo devs, anyone who ships without code review ⏱ ~3 min beginner

Quand l'utiliser : About to commit. Want a second pair of eyes to catch obvious smell before the commit lands.

Prérequis

Local repo with staged changes — git add -p as usual, then ask the agent

Déroulement

Read the staged diff

Show me my staged changes. Flag anything that looks like: debug logs, commented code, hardcoded secrets, or changes unrelated to the stated commit goal '<GOAL>'.✓ Copié

→ Specific file:line flags
Suggest a commit message

Write a commit message following conventional commits. First line under 60 chars, body explains why not what.✓ Copié

→ Copy-pasteable message
Confirm scope

Based on the diff, is this commit appropriately small? Suggest splits if it touches multiple concerns.✓ Copié

→ Go/no-go with rationale

Résultat : A cleaner commit with fewer 'oops' follow-ups.

Pièges

Agent misses secrets because they don't look obviously secret-shaped — Don't rely on this as a secret scanner — run gitleaks or trufflehog in your pre-commit hook as the real defense
Asking for a commit message biases the agent to approve the diff — Always do the review step BEFORE asking for a message — order matters

Combiner avec : github

Find when and why a specific line broke

👤 Engineers debugging regressions ⏱ ~15 min intermediate

Quand l'utiliser : A test started failing and you need to know which commit introduced the bug.

Déroulement

Narrow the suspect file's history

Show git log for src/checkout/Cart.tsx limited to the last 20 commits. Include author and short message.✓ Copié

→ Compact history with SHAs
Diff the suspicious commits

For the 3 commits that touched the calculateTotal function, show the diff. Focus on math/logic changes, ignore style.✓ Copié

→ Per-commit diff snippets
Form a regression hypothesis

Which commit most likely introduced an off-by-one or rounding bug? Point to the exact line and explain your reasoning.✓ Copié

→ Specific SHA + line with rationale

Résultat : A precise commit-level hypothesis you can confirm with git revert + re-run tests.

Pièges

Rename-heavy history loses the trail at renames — Use git log --follow mentality — ask the agent to include the commit that renamed the file and look at that commit's pre-rename path

Combiner avec : github

List and categorize stale local branches

👤 Anyone whose `git branch` output is pages long ⏱ ~10 min beginner

Quand l'utiliser : Quarterly cleanup — too many branches, unclear which are safe to delete.

Déroulement

List all local branches

List every local branch with its last commit date and message.✓ Copié

→ Table of branches
Classify each

Classify: 'merged' (ancestor of main), 'stale' (no commit in 60+ days), 'active' (commit in last 30 days). Flag any that look like abandoned experiments.✓ Copié

→ Categorized list
Propose deletions

Give me the git branch -d command for everything safe to delete. Flag anything that needs -D (force) and explain why.✓ Copié

→ Copy-pasteable cleanup commands

Résultat : A pruned branch list with confidence you're not dropping work.

Pièges

Agent suggests -D for branches that actually have unique commits not on main — Always eyeball the force-delete list manually — one git reflog recovery is cheap but annoying

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

git + github

Local git review before pushing, then open a PR with the same context

Review my staged changes. If they look good, commit with a descriptive message, push the branch, and open a PR on GitHub.✓ Copié

git + filesystem

Code changes + git history in one reasoning loop

Read src/auth/login.ts and the last 5 commits that touched it. Explain why the retry logic was added.✓ Copié

Outils

Ce que ce MCP expose

Outil	Entrées	Quand appeler	Coût
git_status	repo_path	First call of any session — understand what's dirty	free
git_diff_unstaged	repo_path, context_lines?	Review unstaged changes before `git add`	free
git_diff_staged	repo_path, context_lines?	Review what's about to be committed	free
git_diff	repo_path, target, context_lines?	Compare current branch to target (e.g. main, HEAD~5)	free
git_log	repo_path, max_count?, start_timestamp?, end_timestamp?	History browsing — pair with max_count to limit token use	free
git_show	repo_path, revision	Inspect a specific commit	free
git_commit	repo_path, message	Create a commit from staged changes — DISABLE for read-only setups	free
git_add	repo_path, files: string[]	Stage specific files — prefer over git_add . for agent safety	free
git_reset	repo_path	Unstage everything — dangerous, usually skip	free
git_create_branch	repo_path, branch_name, base_branch?	Start a new branch for a task	free
git_checkout	repo_path, branch_name	Switch branches	free
git_branch	repo_path, branch_type, contains?, not_contains?	List branches, filter by containing a commit	free

Coût et limites

Coût d'exécution

Quota d'API: None — all local
Tokens par appel: 200–5000 per diff depending on size
Monétaire: Free
Astuce: Large diffs blow up token costs fast. Use context_lines: 1 or filter by path in your prompt before asking the agent to read the whole thing.

Sécurité

Permissions, secrets, portée

Stockage des identifiants : None — no credentials

Sortie de données : None — server is 100% local, no network calls

Dépannage

Erreurs courantes et correctifs

fatal: not a git repository

The --repository path doesn't point at a git repo. Verify with ls <path>/.git — the directory must exist.

Vérifier : ls <repo_path>/.git/HEAD

Empty diff output despite uncommitted changes

Check staged vs unstaged — git_diff_unstaged and git_diff_staged are separate tools. Use git_status first to see what's where.

git_commit fails with 'Please tell me who you are'

Set git config in the repo: git config user.email ... and git config user.name .... The MCP uses your existing git config.

Vérifier : git config --get user.email

Huge diff burns tokens

Pass context_lines: 0 or 1, or ask the agent to summarize file-by-file first before reading full diffs.

Alternatives

Git vs autres

Alternative	Quand l'utiliser	Compromis
GitHub MCP	You want remote history (PRs, review comments, Actions) not just local	Needs a PAT and makes network calls; more powerful but more surface area
filesystem MCP + shell	You need operations beyond git (grep, find, build commands)	Much broader blast radius — stick with git MCP if git is all you need

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills