Git MCP Server
The reference server for local git — status, diff, log, commit, and branch operations on repositories you point it at. Your history becomes agent-writable, which is most of the point and all of the risk.
What it actually does
Part of the official reference collection, this exposes local git operations over MCP: read status and diffs, search logs, stage, commit, create and switch branches — on repositories you explicitly pass it. It's the difference between an agent that edits files and one that participates in version control: work lands as inspectable commits instead of a mystery working tree. The write operations are the ones to respect. A commit is easy to revert; a confused agent switching branches mid-task is a harder afternoon. Like the rest of the reference set, the source is short enough to actually read before trusting it.
Install
Read the source before you run this. Yes, actually.
From the desk
The Sunnyvale take
The disciplined sibling of the filesystem server: instead of raw file writes, changes arrive as commits with messages, which is how you actually want an agent to touch a codebase. Just remember that git is also a tool for losing work quickly.
Why it matters
Version control is where agent work becomes reviewable. Commit-shaped output — diffable, revertable, attributable — is the safest interface an agent can have to your code.
In practice
Pair it with the filesystem server on one project: files change, then the agent stages and commits with a real message — your review becomes 'git log' instead of a directory diff.
The skeptic's note
It's local git only — no pushing, no PRs, no remotes. For GitHub itself you want GitHub's own server; this one ends at your .git directory.
Use cases
- Agent commits its own work in reviewable increments
- Repo archaeology — log and diff questions in plain language
- Branch-per-task workflows driven by the agent
Risks & caveats
Scoped to the repositories you pass as arguments, but within them it can stage, commit, and move branches. Point it at clones you can afford to re-clone, and keep it away from repos with uncommitted work you care about.
Related tools
Full indexSame shelf, different trade-offs.
GitHub MCP Server
GitHub's official MCP server — lets an agent read repos, file issues, and push code with your credentials, which is exactly as useful and as dangerous as it sounds.
Filesystem MCP Server
The reference server that gives an agent read/write access to your disk, fenced to directories you name. Simple, official, and the single sharpest tool in the drawer.
Context7
Feeds your agent current, version-specific library docs instead of whatever it half-remembers from training. Fixes a real failure mode — by routing your questions through someone else's service.