Pare Git
Give agents reliable typed JSON for git status, log, diff, branch, commit, and push during day-to-day coding.
Overview
Pare Git is an MCP server for the Build phase that exposes local git status, log, diff, branch, commit, and push as structured JSON.
What is this MCP server?
- Covers git status, log, diff, branch, commit, and push as typed JSON
- Stdio MCP via @paretools/git npm package (v0.8.1)
- Matches the Pare pattern of structured devtool responses
- Supports agent-driven branch and commit workflows without shell ambiguity
- Complements Pare GitHub when you move from local commits to remote PRs
- Server version 0.8.1
- npm package identifier @paretools/git
- stdio MCP transport
Community signal: 128 GitHub stars.
What problem does it solve?
Agents misread git CLI output and unsafe push suggestions when diffs and branch state are only available as messy terminal text.
Who is it for?
Solo developers who want agent-assisted git hygiene on a local clone without leaving the MCP tool loop.
Skip if: Teams that only work through a web UI with no local git binary or who need full code hosting features without a GitHub MCP.
What do I get? / Deliverables
Once Pare Git is registered, agents work from consistent JSON for repo state and can script commits and pushes with clearer guardrails.
- JSON-encoded repo status and diff summaries
- Structured log and branch metadata for agent decisions
- Machine-readable results from commit and push attempts
Recommended MCP Servers
Journey fit
How it compares
Structured local git MCP bridge, not a replacement for GitHub's API or a code-review methodology skill.
Common Questions / FAQ
Who is Pare Git for?
Builders using local git repos who want coding agents to read and act on version control state through typed MCP tools.
When should I use Pare Git?
Use it during implementation when you need status, diffs, commits, branches, or push operations driven from an agent with JSON results.
How do I add Pare Git to my agent?
Install @paretools/git from npm, add the stdio MCP entry in your client, and run it in a directory with a valid git repository.