Pare Git MCP server
Pare Git ג€” Structured git operations (status, log, diff, branch, commit, push) as typed JSON.
138 stars
Reviews
Write oneNobody has reviewed Pare Git yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Pare Git tools (20, 1 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
addStages files for commit. Returns structured data with count and list of staged files. Use instead of running `git add` in the terminal.
blameShows commit annotations for a file, grouped by commit. Returns structured blame data with deduplicated commit metadata (hash, author, date) and their attributed lines. Use instead of running `git blame` in the terminal.
branchLists, creates, or deletes branches. Returns structured branch data. Use instead of running `git branch` in the terminal.
checkoutSwitches branches or restores files. Returns structured data with ref, previous ref, and whether a new branch was created. Use instead of running `git checkout` in the terminal.
cherry-pickApplies specific commits to the current branch. Returns structured data with applied commits and any conflicts. Use instead of running `git cherry-pick` in the terminal.
commitwrite actionCreates a commit with the given message. Returns structured data with hash, message, and change statistics. Use instead of running `git commit` in the terminal.
diffReturns file-level diff statistics as structured data. Use full=true for patch content. Use instead of running `git diff` in the terminal.
logReturns commit history as structured data. Use instead of running `git log` in the terminal.
mergeMerges a branch into the current branch. Returns structured data with merge status, fast-forward detection, conflicts, and commit hash. Use instead of running `git merge` in the terminal.
pullPulls changes from a remote repository. Returns structured data with success status, summary, change statistics, and any conflicts. Use instead of running `git pull` in the terminal.
pushPushes commits to a remote repository. Returns structured data with success status, remote, branch, and summary. Use instead of running `git push` in the terminal.
rebaseRebases the current branch onto a target branch. Supports abort and continue for conflict resolution. Returns structured data with success status, branch info, conflicts, and rebased commit count. Use instead of running `git rebase` in the terminal.
remoteLists remote repositories with fetch and push URLs. Returns structured remote data. Use instead of running `git remote -v` in the terminal.
resetUnstages files by resetting them to a ref (default: HEAD). Returns structured data with the ref and list of unstaged files. Use instead of running `git reset` in the terminal.
restoreDiscards working tree changes or restores files from a specific commit. Returns structured data with restored files, source ref, and staged flag. Use instead of running `git restore` in the terminal.
showShows commit details and diff statistics for a given ref. Use instead of running `git show` in the terminal.
stashPushes, pops, applies, or drops stash entries. Returns structured result with action, success, and message. Use instead of running `git stash` in the terminal.
stash-listLists all stash entries with index, message, and date. Returns structured stash data. Use instead of running `git stash list` in the terminal.
statusReturns the working tree status as structured data (branch, staged, modified, untracked, conflicts). Use instead of running `git status` in the terminal.
tagLists tags sorted by creation date. Returns structured tag data with name, date, and message. Use instead of running `git tag` in the terminal.
Public scan report
scanner v0.1.10 · 2026-09-28 · same rubric, same numbers if you re-run it
- Code scan53 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 6 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Install Pare Git in Claude Code, Cursor or VS Code
Runs npx -y @paretools/git on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add pare-git -- npx -y @paretools/git
What the publisher says
From the Pare Git repository's README, as published. We do not edit it. Read it on GitHub
Pare
Reliable, structured CLI output for AI agents — no more parsing fragile terminal text.
Pare provides MCP servers that wrap common developer tools (git, npm, docker, test runners, etc.) and return clean, schema-validated JSON instead of raw terminal text. Agents get typed data they can act on directly, without brittle string parsing.
The Problem
Parsing CLI output is fragile. Raw terminal text includes ANSI escape codes, decorative headers, progress bars, locale-specific formatting, and platform differences that break agent workflows in subtle ways. An agent that works fine with git status on macOS may fail on Windows because the output format changed. A test runner's summary line might shift between versions, silently breaking a regex.
Pare eliminates this entire class of errors by returning schema-validated JSON with consistent field names, regardless of platform, tool version, or locale. As a bonus, structured output is significantly smaller — agents use fewer tokens per tool call:
Token estimates use ~4 chars/token. The biggest savings appear on verbose commands (builds, installs, tests). For simpler tools like eslint or tsc, the main advantage is reliable structured data — agents can use typed JSON directly rather than parsing strings.
How It Works
Each Pare tool returns two outputs:
- content — human-readable text, for MCP clients that display it
- structuredContent — typed, schema-validated JSON, ready for agents to process
This uses MCP's structuredContent and outputSchema features to provide type-safe, validated data that agents can rely on without custom parsing.
Example: git status
Raw git output (~118 tokens):
On branch main
Your branch is ahead of 'origin/main' by 2 commits.
(use "git push" to publish your local commits)Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Pare Git: common questions
- Is Pare Git MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the Pare Git safety report
- How do I install Pare Git?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Pare Git need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Pare Git maintained?
- The last commit was 21 days ago (2026-09-22). The latest release is v0.8.1.
- What can I use instead of Pare Git?
- Servers from other publishers that do the same job: Git MCP server, diffctx MCP server and Nexusmem MCP server. Compare all Pare Git alternatives.
Alternatives to Pare Git
Same job from other publishers: the closest match first, then the best rated.
- GitComprehensive Git MCP server enabling native git tools including clone, commit, worktree, & more.not reviewedEstablishedA
diffctxSelects the minimum code an LLM needs to review a git diffnot reviewedGrowingA- NexusmemLocal-first memory for AI coding agents: shell history with exit codes, git diffs, docs, MCP.not reviewedGrowingA
EmfirgeGit branch for your cloud. Understand AWS risk, prove fixes, and ship safer changes.not reviewedGrowingA
RepowiseCodebase intelligence for AI coding agents — graph, git history, docs, decisions, code health.not reviewedEstablishedB
