Best for
- Developers using AI coding tools like Claude Code, Cursor
- Agent workflows needing reliable git data
P
Pare Git
Community
Structured Git MCP server optimized for AI agents
- Category
- Dev Tools #280 of 438
- Stars
- ★ 138 Popular
- Transport
- stdio (local process)
- Runtime
- Node.js 20+
- Credentials
- No credential needed
- License
- MIT
- Last commit
48FMRS · D
Pare Git provides structured output for git operations, reducing tokens and improving reliability. Suitable for AI agents, but careful configuration of tool selection is needed to avoid unintended actions.
Strongest · Setup experience 14/20 Weakest · Reliability 6/20
Why each score
- Reliability 6/20
- The manifest and README plausibly describe a stdio npm package that wraps git commands into structured JSON, but no source, tests, or CI configuration for packages/server-git were supplied, so the MCP init handshake, tool list, and actual tool behavior cannot be verified. Tests/docs from the other 26 sibling servers must not be attributed here. Static calibration caps reliability at 12, and missing reproducible evidence lowers it to 6.
- Security and permissions 6/20
- No malware, credential theft, covert exfiltration, or other red-line evidence is present, so the 0-4 range does not apply. However, mutating git tools such as commit, push, add, and checkout appear enabled by default with no confirmation mechanism; least privilege is only achievable through the optional PARE_GIT_TOOLS environment variable. Credential handling (e.g., git credential helpers) is undisclosed, so permissions, confirmation, and data-flow disclosure are incomplete; scored 6.
- Maintenance 8/20
- The repository is not archived, the license is MIT, and the manifest version is 0.22.0, indicating the project is not dormant. But apart from stars (which are not scored) and 17 open issues, there is no evidence of commit frequency, release cadence, dependency updates, or a security-response channel. Versioning exists, yet governance and the update path are unclear; scored 8.
- Documentation 14/20
- The README includes install commands, JSON MCP configuration examples, tool-filtering rules, environment variables, platform caveats (Node>=20, Windows cmd /c npx), a troubleshooting table, a structured git status example, and token-efficiency comparisons. However, detailed per-tool schemas, parameter descriptions, and further examples live in external docs/tool-schemas links that were not provided, and per-tool permissions/limits are not documented; therefore not full marks, scored 14.
- Setup experience 14/20
- A single npx command is documented, supported by client setup guides and a JSON MCP configuration example with env filtering, plus Node version and Windows wrapper notes. The install path is clear and short, but no CI or test files were supplied as verifiable execution evidence; static calibration caps setup at 15, so scored 14.
Static review · not runListed 2026-08-07
Read the FMRS scoring method →Fit and risk
What it can accessReads local filesWrites / deletes local filesRuns commands or code
Not for
- Scenarios requiring interactive git features
- Users with special reliance on raw git output
Required permissions
- Access to local git repositories
- Ability to execute git commands
Risks and side effects
- Limited tool selection
- Potential for destructive operations (e.g., push)
Setup
Before you start
Runtime：Node.js 20+
Other optional settings (3)
PARE_GIT_TOOLS
Per-server filter listing which git tools to register, as comma-separated tool names (e.g. status,log,diff); set in the env key of your MCP config.
PARE_TOOLS
Universal tool filter across all servers using server:tool format (e.g. git:status,npm:install); takes precedence over per-server vars.
MCP_TIMEOUT
MCP connection timeout in milliseconds (e.g. 30000), used to fix connection timeouts in Claude Code.
Install via npx: npx -y @paretools/git. Requires Node.js >= 20. Tool selection via PARE_GIT_TOOLS environment variable.
Check that it works
Confirm the pare-git tools (e.g. git status, git log) appear in your client's MCP tool list, then run npx @paretools/init doctor or ask the agent for git status — it should return structured JSON with fields like branch, staged, and untracked.
Troubleshooting
- If npx not found, use cmd /c npx wrapper (Windows)
- Slow first start: precache or install globally
- Node.js version too low: upgrade to 20+
- PATH issues: use absolute path to npx
- Connection timeout: increase client initTimeout
Things to try
Once connected, you can ask your AI assistant things like:
- Show the git status of this repo, including staged and untracked files
- Show the log of the last 5 commits with change stats
- Commit my changes and push to the remote main branch
- Diff the current branch against main
Use cases
AI agents needing structured git status and log
Reducing token consumption for git commands
Cross-platform consistent output
Overview
Pare Git is part of the Pare project, an MCP server for Git operations (status, log, diff, branch, commit, push) that returns typed, schema-validated JSON instead of raw terminal text, enabling agents to act directly without brittle string parsing.
Similar servers
Context7
80 · B
Upstash's official server providing up-to-date third-party library docs for AI coding assistants
NPM Sentinel MCP Server
79 · B
AI-powered NPM package analysis MCP server
MartinLoop MCP Server
79 · B
An independent control layer that gives AI coding agents budgets, brakes, and receipts
GitHub MCP Server
76 · B
GitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
More servers from this repository
Source revision 57e1980e8375 Data synced 2026-10-12 Read the FMRS scoring method