Git MCP server

by selfagency·io.github.selfagency/git-mcp·v0.4.2

No reviews yet

A Git MCP server that doesn't suck

B83/100grade B

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

B83/100

full report

Adoption

Growing

0 stars27 downloads/wk

Reviews

Write one

Nobody has reviewed Git yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Git tools (23, 2 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

git_analytics
Read-only repository analytics computed from local git history. Use action=contributors|churn|activity|summary|file-stats.
git_bisect
Bisect: start, good, bad, skip, run, or reset.
git_branches
Branch tool. Use action=list|create|delete|rename|checkout|set_upstream|recent for branch workflows.
git_cherry_pick
Cherry-pick: start, continue, or abort.
git_commits
Commit-area tool. Use action=add|restore|commit|reset|revert|undo|nuke|wip|unstage|amend.
git_context
Context/config tool. Use action=summary|search|get_config|set_config|aliases for repo context operations.
git_docs
Search and browse official Git documentation from git-scm.com. Use action="search" to find relevant commands and concepts by keyword. Use action="man" to fetch the full man page for a specific git command (e.g. query="commit" fetches the git-commit man page). Useful for answering questions about how to use git commands, understanding options, and discovering the right git command for a task.
git_flow
Drives the git-flow-next CLI. The CLI owns the workflow semantics \u2014 the finish state machine, conflict recovery, and worktree lifecycle \u2014 so it must be installed and on PATH; this tool only builds argv. Prefer operation=config/topic/control with subactions; the legacy action aliases remain for compatibility.
git_history
History tool. Use action=log|show|reflog|blame|lg|who to inspect commits, refs, and contributors.
git_lfs
Manage Git Large File Storage (LFS). Supports tracking/untracking file patterns, listing LFS-tracked files and status, pulling/pushing LFS objects, installing LFS hooks for the repository, and migrating existing files into or out of LFS storage.
git_merge
Merge: start, continue, or abort.
git_ping
Returns a simple response to verify the server is running.
git_prwrite action
Create, list, or merge pull requests / merge requests on the detected forge provider (GitHub, GitLab, Forgejo, Gitea, Bitbucket). Uses the provider CLI (gh/glab/tea) when installed, otherwise the provider REST API with a *_TOKEN env var.
git_rebase
Rebase: start, continue, abort, or skip.
git_remotes
Remote tool. Use action=list|manage|fetch|pull|push for network/transport operations.
git_rewrite
Rewrite commit history. Use action=reword|squash|rewrite-messages|backup|restore. History rewriting changes commit hashes and requires force-push; create a backup first.
git_stash
Stash, list, apply, pop, or drop stashes.
git_status
Status and diff tool. Use action=status|diff|diff_main to inspect working tree and branch deltas.
git_submodule
Submodule: add, list, update, sync, or set_branch.
git_tag
Tag: list, create, or delete.
git_workflowwrite action
Run named multi-step Git workflows with resumable lifecycle controls. Use action=start|status|continue|abort|list with workflow families such as snapshot, replay, branch_surgery, and publish.
git_workspace
Workspace tool for stash/rebase/cherry-pick/merge/bisect/tag/worktree/submodule actions plus stash_all shortcut.
git_worktree
Worktrees, two ways. Path-addressed (add, remove, lock, unlock, prune, repair) drives plain git worktree and needs nothing but git. Branch-addressed (flow_add, flow_remove, flow_list, flow_path) drives git flow worktree: it addresses worktrees by branch name, computes paths from the gitflow.worktreePath template, and tags provenance so cleanup can tell a git-flow-created worktree (removed) from a

Public scan report

scanner v0.1.10 · 2026-10-14 · same rubric, same numbers if you re-run it

no findings

Code scan6 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 qualitystatic API keys via environment variables6/15
Maintenancelast push 0 days ago15/15
Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

How Git compares

Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 83/100; higher than 65% of 1,119 Developer tools servers
Tools: 23; the typical Developer tools server has 7
Tools that change things: 9%; typical: 5%. Fewer write tools means less an agent can break
Downloads a week: 27; more than 10% of 436 Developer tools servers with a package

What its tools let an agent do: 21 read · 2 change

Install Git in Claude Code, Cursor or VS Code

Runs npx -y @selfagency/git-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add git-mcp -- npx -y @selfagency/git-mcp

Add to Cursor

What the publisher says

From the Git repository's README, as published. We do not edit it. Read it on GitHub

git-mcp

A Git MCP server that doesn't suck

Exposes the full Git workflow to any MCP-compatible AI agent — inspect, write, branch, remote, stash, rebase, LFS, git-flow, documentation lookup, and more. Designed to be safe by default, composable, and fast. Powered by simple-git.

Built for coding agents in tools like GitHub Copilot, Claude Code, Cursor, and OpenAI Codex, while remaining compatible with any MCP client that can call tools and resources.

Features

18 tools with 80+ actions covering everyday Git workflows, advanced recovery, history rewriting, repository analytics, forge pull requests, and external VCS awareness
Safety-first — destructive operations require explicit confirmation; force push and hook bypass are opt-in via server config
GPG/SSH signing for commits and tags, with server-level auto-sign support
Git LFS — track patterns, manage objects, install hooks, migrate history
Git Flow — drives the git-flow-next CLI, so the finish state machine, conflict recovery, and worktree lifecycle stay correct as the CLI evolves. Preset init, overview, config CRUD, generalized topic actions, and classic feature/release/hotfix/support aliases
Documentation lookup — search git-scm.com and fetch man pages directly from the LLM
MCP Resources — URI-addressable read-only views of status, log, branches, and diff
Bundled agent skill — skills/git-mcp-workflow/ documents MCP-first Git workflows, recovery, worktrees, releases, and advanced operations for AI agents and coding agents; installable via skills-npm and skill.sh
External VCS awareness — gitbutcheck / gitjjcheck detect GitButler and Jujutsu and guide agents to prefer their native CLIs/MCP (with but teardown guidance) over git-mcp tools when appropriate
History rewrite — git_rewrite: reword, squash, rewrite-messages, and backup/restore for safe commit-history rewriting
Repository analytics — git_analytics: contributors, churn, activity, summary, and file-stats computed from local git history
Pull requests — git_pr: create/list/merge PRs/MRs on GitHub, GitLab, Forgejo, Gitea, and Bitbucket via provider CLI or REST API

Quick Start

npx (no install)

npx @selfagency/git-mcp --repo-path /path/to/your/repo

Install globally

npm install -g @selfagency/git-mcp
git-mcp --repo-path /path/to/your/repo

Claude Desktop

Add to ~/Library/Application Support/Claude/claudedesktopconfig.json:

{
  "mcpServers": {
    "git": {
      "command": "npx",
      "args": ["-y", "@selfagency/git-mcp", "--repo-path", "/path/to/your/repo"]
    }
  }
}

VS Code (Copilot)

Add to .vscode/mcp.json in your project:

{
  "servers": {
    "git": {
      "command": "npx",
      "args": ["-y", "@selfagency/git-mcp", "--repo-path", "${workspaceFolder}"]
    }
  }
}

Configuration

All configuration is via environment variables. Pass them in your MCP client config:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Git: common questions

Is Git MCP server safe?: Mostly: it is graded B (83/100). Read the Git safety report
How do I install Git?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Git need an API key?: Yes. The registry entry asks for GIT_SIGNING_KEY.
Is Git maintained?: The last commit was 21 days ago (2026-10-14). The latest release is v0.4.2.
What can I use instead of Git?: Servers from other publishers that do the same job: Repowise MCP server, Gitwand MCP server and Palinode MCP server.
How does Git compare with other Developer tools MCP servers?: safety score 83/100 (higher than 65% of 1,119 Developer tools servers); tools 23 (the typical Developer tools server has 7); tools that change things 9% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Git

Same job from other publishers: the closest match first, then the best rated.

Repowise
Codebase intelligence for AI coding agents — graph, git history, docs, decisions, code health.
not reviewed
Established
B
Gitwand
Auto-resolves Git merge conflicts so agents only touch the complex hunks.
not reviewed
Established
A
Palinode
Inspectable, correctable project memory in git-versioned Markdown for AI agents.
not reviewed
Established
C
Contentrain
Git content governance, 23 deterministic MCP tools. Hosted: docs.contentrain.io/developer/mcp-cloud
not reviewed
Established
C
Kindex
Persistent knowledge graph and MCP server for AI workflows with git-tracked project context.
not reviewed
Established
A

Run it through the gateway

Local package. It runs on your machine, not through the gateway.

Rating: —
Safety grade: B · 83/100
Stars: 0
Downloads/wk: 27
Price: Free
Licence: MIT
Transport: Local · npm
Version: 0.4.2
Category: Developer tools
Last release: 2026-10-14

Credentials it needs

GIT_REPO_PATHDefault repository path for all tool requests. Can also be set via the --repo / --repo-path CLI argument. If omitted, each tool call must supply repo_path explicitly.
GIT_ALLOW_NO_VERIFYSet to 'true' to expose a no_verify parameter on commit and push tools, passing --no-verify to Git and bypassing pre-commit / pre-push hooks.
GIT_ALLOW_FORCE_PUSHSet to 'true' to expose a force parameter on push tools. Remote branch protection rules (GitHub/GitLab) are still enforced server-side regardless.
GIT_ALLOW_FLOW_HOOKSSet to 'true' to allow git_flow to execute git-flow-next-compatible hook and filter programs discovered from git config or repository hook locations.
GIT_SIGNING_KEYsecretDefault signing key: a GPG key ID, an SSH public key path, or empty to use git's configured user.signingkey. Used when GIT_AUTO_SIGN_COMMITS or GIT_AUTO_SIGN_TAGS is enabled.
GIT_SIGNING_FORMATSigning format for commits and tags. Accepted values: openpgp, ssh, x509.
GIT_AUTO_SIGN_COMMITSSet to 'true' to automatically sign all commits produced by this server.
GIT_AUTO_SIGN_TAGSSet to 'true' to automatically sign all tags produced by this server.

Own this server?

Claim it to keep the listing current and reply to reviews. Claiming never changes the grade or hides a review.

Claim listing

Badge for your README

Shows the safety grade and links back to this page. It updates itself after every scan and review.

[![mcp.market](https://mcp.market/badge/selfagency-git-mcp.svg)](https://mcp.market/server/selfagency-git-mcp)

How the badge works