The Git MCP Server — Anthropic's Official Reference (With the Missing Push Button)

Source: Dev.to

At a glance

~81,700 stars (monorepo), 12 tools, ~256 K weekly PyPI downloads, 2.4 M PulseMCP all‑time (#17 globally). Rating: 3/5

Twelve tools. No push. That’s the Git MCP server in a nutshell.

The 12 Tools

git_status
git_diff_unstaged
git_diff_staged
git_diff
git_add
git_reset
git_commit
git_log
git_show
git_create_branch
git_checkout
git_branch

Everything you need for local repository work, up to and including committing — then it hands you back the keyboard.

What Works

• Zero‑dependency setup — no API keys, no accounts, point at a repo and go.
• Security‑hardened after three CVEs patched by December 2025 (flag injection prevention, path validation, git_init removed).
• Well‑designed diffs — three separate tools for unstaged, staged, and ref comparison.
• Date‑based log filtering — start_timestamp/end_timestamp for “what changed last week”.
• 100 % test coverage.

What Doesn’t Work

• No push, pull, or fetch — Issue #618 open 13 months, PR #2961 untouched since Nov 2025.
• No merge or rebase — can create branches but can’t integrate work back.
• No stash, tag, or blame — essential operations missing.
• git_reset is all‑or‑nothing — can’t unstage specific files.
• stdio only — no HTTP/SSE transport.

Three CVEs (All Patched)

CVE‑2025‑68143 (CVSS 8.8)

git_init accepted arbitrary paths. Fix: removed entirely.

CVE‑2025‑68144 (CVSS 8.1)

Argument injection in git_diff/git_checkout. Fix: input sanitization.

CVE‑2025‑68145 (CVSS 7.1)

Path traversal bypass in --repository. Fix: proper validation.

These could be chained with the Filesystem MCP server for RCE via Git’s smudge/clean filter mechanism.

vs. Community Alternatives

• cyanheads/git-mcp-server (199 stars, 28 tools) — push, pull, merge, rebase, stash, tag, blame, clone, worktree. Stdio + Streamable HTTP. Apache 2.0.
• GitKraken MCP Server — git + multi‑platform issue tracking (GitHub, GitLab, Bitbucket, Azure DevOps, Jira).

The Bottom Line

Rating: 3/5 — Solid implementation of half a git workflow. The 12 tools it ships are well‑built, but missing push/pull/merge makes it a read‑and‑commit server. The community server from cyanheads (28 tools) or GitKraken are better for complete workflows. This is the secure, minimal baseline — just know you’ll need to supplement it.

Originally published on ChatForest. We research servers through documentation and GitHub repos; we do not test hands‑on. About ChatForest.