git-mcp-server MCP — Casos de uso, Instalar & Demo en vivo

Por qué usarlo

Características clave

28 tools across repo mgmt, staging, history, branching, remotes, advanced workflows
Session-scoped working directory — multi-repo agents without env gymnastics
Optional GPG / SSH commit signing
Configurable response format (JSON for agents, Markdown for humans)
Optional JWT or OAuth auth on the MCP transport itself
Optional sandbox base directory — confine operations to GIT_BASE_DIR

Demo en vivo

Cómo se ve en la práctica

git-2.replay ▶ listo

0/0

Instalar

Elige tu cliente

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

{
  "mcpServers": {
    "git-2": {
      "command": "npx",
      "args": [
        "-y",
        "git-mcp-server"
      ],
      "_inferred": true
    }
  }
}

Abre Claude Desktop → Settings → Developer → Edit Config. Reinicia después de guardar.

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

{
  "mcpServers": {
    "git-2": {
      "command": "npx",
      "args": [
        "-y",
        "git-mcp-server"
      ],
      "_inferred": true
    }
  }
}

Cursor usa el mismo esquema mcpServers que Claude Desktop. La configuración del proyecto prevalece sobre la global.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "git-2": {
      "command": "npx",
      "args": [
        "-y",
        "git-mcp-server"
      ],
      "_inferred": true
    }
  }
}

Haz clic en el icono MCP Servers de la barra lateral de Cline y luego en "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "git-2": {
      "command": "npx",
      "args": [
        "-y",
        "git-mcp-server"
      ],
      "_inferred": true
    }
  }
}

Mismo formato que Claude Desktop. Reinicia Windsurf para aplicar.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "git-2",
      "command": "npx",
      "args": [
        "-y",
        "git-mcp-server"
      ]
    }
  ]
}

Continue usa un array de objetos de servidor en lugar de un mapa.

~/.config/zed/settings.json

{
  "context_servers": {
    "git-2": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "git-mcp-server"
        ]
      }
    }
  }
}

Añádelo a context_servers. Zed recarga en caliente al guardar.

claude mcp add git-2 -- npx -y git-mcp-server

Un solo comando. Verifica con claude mcp list. Quita con claude mcp remove.

Casos de uso

Usos del mundo real: git-mcp-server

Apply the same refactor across 10 repos in a monorepo-adjacent org

👤 Platform engineers, devrel ⏱ ~45 min advanced

Cuándo usarlo: You need to bump a dependency or rename an import across many repos and don't want to clone and context-switch manually.

Requisitos previos

Local clones or write access — SSH keys configured

Flujo

Enumerate repos

List every repo under ~/code/acme. For each, switch working directory, run git_status, and tell me the current branch.✓ Copiado

→ Per-repo status
Branch and apply change

In each repo, create branch 'chore/bump-foo', bump foo from 1.x to 2.x in package.json, commit with message 'chore: bump foo', push, and open a PR (via github MCP).✓ Copiado

→ PR URLs for each repo

Resultado: Cross-repo change dispatched in one conversation.

Errores comunes

Commit storm — a bad refactor now lives in 10 PRs — Test on one repo first; only then dispatch to the rest
Sign-off / DCO required but unsigned — Enable GIT_SIGN_COMMITS and set GIT_USERNAME/GIT_EMAIL

Combinar con: github · filesystem

Generate release notes from git log between two tags

👤 Release managers ⏱ ~20 min intermediate

Cuándo usarlo: Cutting a release and want the changelog written from actual commits, not memory.

Flujo

Fetch tags and diff

Switch to repo ~/code/acme/api. Fetch, then git_log from tag v1.4.0 to HEAD. Group by conventional-commit type.✓ Copiado

→ Grouped commit list
Draft notes

Write release notes in keep-a-changelog format, highlighting breaking changes and contributors.✓ Copiado

→ Markdown changelog draft
Tag the release

Create tag v1.5.0 with these release notes as the tag message. Sign it.✓ Copiado

→ Signed tag created

Resultado: Release published with accurate, readable notes.

Errores comunes

Commit messages are garbage → release notes are garbage — Enforce conventional commits in CI before this step

Combinar con: github

Clean up a feature branch before merge (squash + reword)

👤 Devs with messy WIP branches ⏱ ~15 min intermediate

Cuándo usarlo: You have 14 commits on a feature branch: 'wip', 'fix', 'more fix', 'actually fix it'. You want to squash into 3 logical commits before opening the PR.

Flujo

Inspect

Show git_log for branch 'feat/payments' since it diverged from main.✓ Copiado

→ Commit list
Plan the squash

Propose a 3-commit rewrite plan grouping related work. Don't execute yet.✓ Copiado

→ Plan with commit boundaries + messages
Execute via reset + fresh commits

Execute the plan using git_reset --soft to the merge-base, then git_add + git_commit in 3 logical chunks per the plan.✓ Copiado

→ 3-commit linear history

Resultado: A reviewable PR history.

Errores comunes

Destructive — force-push overwrites collaborators' work — Only do this on solo feature branches; never on shared branches

Combinaciones

Combínalo con otros MCPs para multiplicar por 10

git-2 + github

git_commit + git_push + open PR in one flow

Commit staged changes with message 'X', push, then open a PR on GitHub targeting main.✓ Copiado

git-2 + filesystem

Edit files then commit atomically

Edit src/index.ts replacing foo with bar, git_add the file, git_commit.✓ Copiado

Herramientas

Lo que expone este MCP

Herramienta	Entradas	Cuándo llamar	Coste
git_status	cwd?: str	First step in any session; verify repo state	free
git_log	cwd?, range?, max_count?	Inspect history; use range for release diffs	free
git_diff	cwd?, target?, staged?: bool	Review changes before committing	free
git_add	cwd?, paths[]	Stage specific files — avoid `.` to prevent sensitive file leaks	free
git_commit	cwd?, message, sign?: bool	Create a commit; destructive-ish, so confirm first	free
git_branch	cwd?, action: list\|create\|delete\|rename, name?	Manage branches	free
git_worktree	cwd?, action: add\|list\|remove, path?, branch?	Juggle multiple branches without switching	free
git_push	cwd?, remote?, branch?, force?: bool	Publish commits; `force` is destructive — default to false	network
set_working_directory	path: str	Switch the session's active repo	free

Coste y límites

Lo que cuesta ejecutarlo

Cuota de API: None — all local
Tokens por llamada: git_log/diff outputs can be huge; cap with max_count / paths
Monetario: Free, Apache 2.0
Consejo: Use max_count on git_log and specific paths on git_diff. Full-history log on a big repo = 50k+ tokens.

Seguridad

Permisos, secretos, alcance

Ámbitos mínimos: Local filesystem access to the repos you want managed

Almacenamiento de credenciales: SSH keys in ~/.ssh; set GIT_BASE_DIR to sandbox the MCP

Salida de datos: git push sends to your configured remotes

No conceder nunca: Force push to main/master without confirmation

Session-scoped cwd means if you don't set_working_directory, operations hit the wrong repo. Always check git_status first.
Destructive ops (reset, force-push, branch -D) execute without extra confirmation — phrase prompts defensively.

Resolución de problemas

Errores comunes y soluciones

Permission denied (publickey) on push

SSH key not available to the MCP process. Start ssh-agent with your key loaded.

Verificar: ssh -T [email protected]

Operation outside base directory rejected

You set GIT_BASE_DIR; the requested path escapes it. Move the repo into the base dir or widen it.

Commit signing fails

GPG/SSH signing key not configured. Check git config --get user.signingkey and gpg --list-secret-keys.

Verificar: git commit -S -m test in the repo directly

Wrong repo operated on

Session cwd not set. Always start a session with set_working_directory or pass cwd per call.

Verificar: Call git_status and inspect the returned path

Alternativas

git-mcp-server vs otros

Alternativa	Cuándo usarla	Contrapartida
Official git MCP	You only need basic git ops and want the reference implementation	Fewer tools; no session cwd or signing
GitHub MCP	Your workflow is PR-centric and lives on GitHub	Operates on GitHub API, not local git; complementary

Más

Recursos

📖 Lee el README oficial en GitHub

🐙 Ver issues abiertas

🔍 Ver todos los 400+ servidores MCP y Skills