Git Official
Read repository history, diffs and branches as tools an agent can call.
- Transport
- stdio
- Package
- mcp-server-git
- Registry id
- —
No install snippet on purpose. A working MCP config is a command, its arguments and an environment block — the last two are where API keys live, so this catalogue never stores them and cannot publish them. Follow the link above for the authors' own instructions.
Exposes a local git repository: status, diffs, log, branches, and the contents of a file at a given revision.
What it changes about an agent's answers
Without it, an agent reasons about your code as it is right now and has no idea why any of it looks that way. With history in reach, "why is this check here" is answerable — it can find the commit that added the line and read the message. In practice that is the difference between an agent that rewrites a workaround and one that notices it was deliberate.
Where it fits
Review and archaeology rather than authoring: summarising a branch before a pull request, explaining a regression window, working out what a release actually changed.
Worth knowing
- It reads; it is not a way to let an agent commit and push on your behalf, and you should be glad about that.
- A repository with a very large history will produce very large tool results. Ask for a range rather than the whole log.