@cyanheads/git-mcp-server
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 0 of 1 tool tried
Contacts while installing and starting: nothing
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y @cyanheads/git-mcp-server@2.15.3
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
1 tool that takes no input and looks read-only was called once with nothing. 0 returned a result.
git_status | No usable answer tool reported an error: Error: Error in tool:git_status: ENOENT: no such file or directory, uv_resident_set_memory |
During the calls it contacted nothing it had not already contacted.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
git_add path, paths, update, all, force
Stage files for commit. Add file contents to the staging area (index) to prepare for the next commit.
git_blame path, filePath, startLine, endLine, ignoreWhitespace
Show line-by-line authorship information for a file, displaying who last modified each line and when. For large files, use startLine/endLine to limit output.
git_branch path, mode, branchName, newBranchName, startPoint, force, all, remote, merged, noMerged, limit
Manage branches: list all branches, show current branch, create a new branch, delete a branch, or rename a branch.
git_changelog_analyze path, reviewTypes, maxCommits, maxTags, sinceTag, branch
Gather git history context (commits, tags) and structured review instructions to support LLM-driven changelog analysis. Changelog file should be read separately; this tool provides the supporting git data and analysis framework. Pass one or more review types to control what kind of analysis to perform.
git_checkout path, target, createBranch, force, paths, track
Switch branches or restore working tree files. Can checkout an existing branch, create a new branch, or restore specific files.
23 more tools
git_cherry_pick path, commits, noCommit, continueOperation, abort, mainline, strategy, signoff
Cherry-pick commits from other branches. Apply specific commits to the current branch without merging entire branches.
git_clean path, force, dryRun, directories, ignored
Remove untracked files from the working directory. Requires force flag for safety. Use dry-run to preview files that would be removed.
git_clear_working_dir confirm
Clear the session working directory setting. This resets the context without restarting the server. Subsequent git operations will require an explicit path parameter unless git_set_working_dir is called again.
git_clone url, path, branch, depth, bare, mirror
Clone a repository from a remote URL or local path. Accepts HTTP(S), SSH, git://, file://, and bare filesystem paths, with optional shallow cloning.
git_commit path, message, author, amend, allowEmpty, noVerify, filesToStage
Create a new commit with staged changes in the repository. Records a snapshot of the staging area with a commit message.
**Commit Message Format:**
Pass commit messages as JSON string parameters. Multi-line messages are supported using standard JSON string escaping.
**Examples:**
- Single line: { "message": "feat: add user authentication" }
- Multi-line: { "message": "feat: add user authentication\n\nImplemented OAuth2 flow with JWT tokens.\nAdded tests for login and logout." }
Note: Do not use bash heredoc syntax. Literal escape sequences (\n, \t) in the message string are automatically normalized to their actual characters.git_diff path, target, source, paths, staged, includeUntracked, nameOnly, stat, contextLines, autoExclude
View differences between commits, branches, or working tree. Shows changes in unified diff format.
git_fetch path, remote, prune, tags, depth
Fetch updates from a remote repository. Downloads objects and refs without merging them.
git_init path, initialBranch, bare
Initialize a new Git repository at the specified path. Creates a .git directory and sets up the initial branch.
git_log path, maxCount, skip, since, until, author, grep, branch, filePath, oneline, stat, patch, showSignature
View commit history with optional filtering by author, date range, file path, or commit message pattern.
git_merge path, branch, strategy, noFastForward, squash, message, abort
Merge branches together. Integrates changes from another branch into the current branch with optional merge strategies.
git_pull path, remote, branch, rebase, fastForwardOnly
Pull changes from a remote repository. Fetches and integrates changes into the current branch.
git_push path, remote, branch, force, forceWithLease, setUpstream, tags, dryRun, delete, remoteBranch, confirmed
Push changes to a remote repository. Uploads local commits to the remote branch.
git_rebase path, mode, upstream, branch, interactive, onto, preserve
Rebase commits onto another branch. Reapplies commits on top of another base tip for a cleaner history.
git_reflog path, ref, maxCount
View the reference logs (reflog) to track when branch tips and other references were updated. Useful for recovering lost commits.
git_remote path, mode, name, url, newName, push
Manage remote repositories: list remotes, add new remotes, remove remotes, rename remotes, or get/set remote URLs.
git_reset path, mode, target, paths, confirmed
Reset current HEAD to specified state. Can be used to unstage files (soft), discard commits (mixed), or discard all changes (hard).
git_set_working_dir path, validateGitRepo, initializeIfNotPresent
Set the session working directory for all git operations so subsequent calls can omit the path parameter. Always returns a repository snapshot (status, recent commits, recent tags, remotes) to orient the caller.
git_show path, object, format, stat, filePath
Show details of a git object (commit, tree, blob, or tag). Displays commit information and the diff of changes introduced.
git_stash path, mode, message, stashRef, includeUntracked, keepIndex, limit
Manage stashes: list stashes, save current changes (push), restore changes (pop/apply), or remove stashes (drop/clear).
git_status path, includeUntracked
Show the working tree status including staged, unstaged, and untracked files.
git_tag path, mode, tagName, commit, message, annotated, force, limit
Manage tags: list all tags, create a new tag, delete a tag, or verify a signed tag. Tags are used to mark specific points in history (releases, milestones). Verify runs `git tag -v` and returns a structured result distinguishing unsigned tags, missing trust configuration, bad signatures, and valid signatures.
git_worktree path, mode, worktreePath, branch, commitish, force, newPath, detach, verbose, dryRun
Manage multiple working trees: list worktrees, add new worktrees for parallel work, remove worktrees, or move worktrees to new locations.
git_wrapup_instructions acknowledgement, createTag
Returns a Git wrap-up protocol: an acceptance-criteria checklist the agent must satisfy before the session is considered shipped. Uses the operator's custom instructions if configured, otherwise emits a generic goals-strict/mechanism-generic default. Enriches the response with a repository snapshot (status, recent commits, recent tags) so the agent has immediate orientation for the commit and release steps.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | Apache-2.0 |
|---|---|
| Needs | node >=20.0.0 |
| Source | github.com/cyanheads/git-mcp-server |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-+Bj0UvHAOCidGX7We1FYPXs/S751jOz6+aH44nR05BUEG4+Zu0hLLj7AjUKepqN99qHvXgqEzeSW+5utoYBQgA== |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40cyanheads/git-mcp-server)
New version out? Ask for a fresh report.