Git History MCP server
io.github.tonyweckstrom1987/git-history·v1.1.1Give AI agents Git history tools: commit search, file history, blame, contributors, ref diffs.
0 stars5 downloads/wk
Reviews
Write oneNobody has reviewed Git History yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Git History tools (7)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
blame_fileHakee tiedoston rivikohtaisen 'git blame' -tiedon: kuka ja missä commitissa kunkin rivin viimeksi kirjoitti.
get_commit_diffHakee tietyn commitin koko diffin (kaikki tiedostomuutokset). Käytä kun haluat nähdä TARKALLEEN mitä muuttui.
get_contributorsHakee yhteenvedon repositorion committaajista ja heidän commit-määristään (kuten 'git shortlog -sn').
get_diff_between_refsHakee diffin kahden commitin, branchin tai tagin välillä, valinnaisesti rajattuna yhteen tiedostoon.
get_file_historyHakee tiedoston muutoshistorian: milloin sitä on muokattu, kuka muokkasi ja mihin commit-viestiin muutos liittyi.
get_recent_commitsHakee repositorion uusimmat commitit uusimmasta vanhimpaan.
search_commitsEtsii Git-commiteja joiden commit-viesti sisältää annetun hakusanan (esim. bugin numero tai avainsana).
Public scan report
scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it
- Code scan3 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner6/10
How Git History compares
Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 89/100
- higher than 80% of 1,119 Developer tools servers
- Tools
- 7
- the typical Developer tools server has 7
- Tools that change things
- 0%
- typical: 5%. Fewer write tools means less an agent can break
- Downloads a week
- 5
- more than 1% of 436 Developer tools servers with a package
What its tools let an agent do: 7 read
Install Git History in Claude Code, Cursor or VS Code
Runs npx -y mcp-server-git-history on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add git-history -- npx -y mcp-server-git-history
What the publisher says
From the Git History repository's README, as published. We do not edit it. Read it on GitHub
mcp-server-git-history
Uusin julkaistu versio: 1.0.1 — https://www.npmjs.com/package/mcp-server-git-history
MCP-palvelin (Model Context Protocol) joka antaa tekoälyagenteille (Claude Desktop, Cursor, Windsurf) työkalut Git-repositorion historian lukemiseen ja hakemiseen.
Ratkaisee ongelman jossa tekoäly näkee koodin nykytilan, mutta ei tiedä miksi jokin muuttui tai kuka teki muutoksen viimeksi.
Quick start
An MCP server that gives AI agents (Claude Desktop, Cursor, Windsurf) tools to read and search Git history — commit search, file history, blame, contributors, and diffs between refs.
Run it directly with npx (no install needed):
npx -y mcp-server-git-history /path/to/your/repoAdd it to Claude Desktop's config (claudedesktopconfig.json):
{
"mcpServers": {
"git-history": {
"command": "npx",
"args": ["-y", "mcp-server-git-history", "/path/to/your/repo"]
}
}
}Restart Claude Desktop, then ask something like "When was src/index.js last changed, and why?"
Työkalut
- searchcommits(query, limit?)** — etsii commiteja hakusanalla commit-viestistä
- getrecentcommits(limit?) — hakee uusimmat commitit (yleiskuva viimeaikaisista muutoksista)
- getcommitdiff(commitHash) — hakee yhden commitin koko diffin
- getfilehistory(filePath, limit?) — hakee tiedoston muutoshistorian (kuka, milloin, miksi)
- blamefile(filePath, startLine?, endLine?)** — rivikohtainen git blame: kuka ja missä commitissa kirjoitti kunkin rivin
- getcontributors(limit?)** — yhteenveto committaajista ja heidän commit-määristään (git shortlog -sn)
- getdiffbetweenrefs(fromRef, toRef, filePath?)** — diffi kahden commitin/branchin/tagin välillä, valinnaisesti yhteen tiedostoon rajattuna
Esimerkkikutsut
{ "name": "search_commits", "arguments": { "query": "login-bugi", "limit": 10 } }{ "name": "get_recent_commits", "arguments": { "limit": 5 } }{ "name": "get_commit_diff", "arguments": { "commitHash": "a1b2c3d" } }{ "name": "get_file_history", "arguments": { "filePath": "src/index.js", "limit": 10 } }{ "name": "blame_file", "arguments": { "filePath": "src/index.js", "startLine": 10, "endLine": 25 } }{ "name": "get_contributors", "arguments": { "limit": 10 } }{ "name": "get_diff_between_refs", "arguments": { "fromRef": "main", "toRef": "HEAD", "filePath": "src/index.js" } }Asennus Claude Desktopiin
Lisää claudedesktopconfig.json-tiedostoon:
{
"mcpServers": {
"git-history": {
"command": "npx",
"args": ["-y", "mcp-server-git-history", "/polku/repositorioosi"]
}
}
}Repositorion polku voidaan antaa myös GITREPOPATH-ympäristömuuttujalla, tai jättää pois jolloin käytetään palvelimen käynnistyshakemistoa.
Käynnistä Claude Desktop uudelleen, ja kysy esimerkiksi: "Milloin tiedostoa src/index.js on viimeksi muokattu ja miksi?"
Asennus Cursoriin
Lisää projektin .cursor/mcp.json-tiedostoon (tai globaaliin ~/.cursor/mcp.json-tiedostoon):
{
"mcpServers": {
"git-history": {
"command": "npx",
"args": ["-y", "mcp-server-git-history", "/polku/repositorioosi"]
}
}
}Avaa Cursorin asetuksista MCP-välilehti ja varmista, että git-history-palvelin on käynnissä (vihreä piste). Sama GITREPOPATH-ympäristömuuttuja ja komentoriviargumentti toimivat kuin Claude Desktopissa.
Kehitys ja testaus paikallisesti
git clone <repo>
cd mcp-server-git-history
npm install
npm test # testaa tätä samaa repoa
node test/manual-test.js /polku/johonkin/git-repoon # tai jotain muuta repoaShortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Git History: common questions
- Is Git History MCP server safe?
- Yes, by our scan: it is graded A (89/100). Read the Git History safety report
- How do I install Git History?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Git History need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Git History maintained?
- The last commit was 39 days ago (2026-09-26). The latest release is v1.1.1.
- What can I use instead of Git History?
- Servers from other publishers that do the same job: Nexusmem MCP server, Pare Git MCP server and Repowise MCP server.
- How does Git History compare with other Developer tools MCP servers?
- safety score 89/100 (higher than 80% of 1,119 Developer tools servers); tools 7 (the typical Developer tools server has 7); tools that change things 0% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Git History
Same job from other publishers: the closest match first, then the best rated.
- NexusmemLocal-first memory for AI coding agents: shell history with exit codes, git diffs, docs, MCP.not reviewedGrowingA
- Pare GitPare Git ג€” Structured git operations (status, log, diff, branch, commit, push) as typed JSON.not reviewedGrowingA
RepowiseCodebase intelligence for AI coding agents — graph, git history, docs, decisions, code health.not reviewedEstablishedB- GitComprehensive Git MCP server enabling native git tools including clone, commit, worktree, & more.not reviewedEstablishedA
- SoloMDRead and search a folder of Markdown notes: search, backlinks, tags, tasks, outlines, git history.not reviewedEstablishedB