All servers / Developer / Git
Git
Secure Git operations for agents.
Tested by ConnectATDScore 90 out of 100. Tested 2026-11-17 on package version 2.15.3. Package: @cyanheads/git-mcp-server · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (6.4 seconds including download)
- Tools offered: 28
- Last published: 2026-08-24
- Weekly downloads (npm): 4,397
- License: Apache-2.0 · Direct dependencies: 3
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
git_add5 of 5 parameters describedStage files for commit. Add file contents to the staging area (index) to prepare for the next commit.
git_blame5 of 5 parameters describedShow 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_branch11 of 11 parameters describedManage branches: list all branches, show current branch, create a new branch, delete a branch, or rename a branch.
git_changelog_analyze6 of 6 parameters describedGather 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_checkout6 of 6 parameters describedSwitch branches or restore working tree files. Can checkout an existing branch, create a new branch, or restore specific files.
git_cherry_pick8 of 8 parameters describedCherry-pick commits from other branches. Apply specific commits to the current branch without merging entire branches.
git_clean5 of 5 parameters describedRemove untracked files from the working directory. Requires force flag for safety. Use dry-run to preview files that would be removed.
git_clear_working_dir1 of 1 parameter describedClear 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_clone6 of 6 parameters describedClone a repository from a remote URL or local path. Accepts HTTP(S), SSH, git://, file://, and bare filesystem paths, with optional shallow cloning.
git_commit7 of 7 parameters describedCreate 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_diff10 of 10 parameters describedView differences between commits, branches, or working tree. Shows changes in unified diff format.
git_fetch5 of 5 parameters describedFetch updates from a remote repository. Downloads objects and refs without merging them.
git_init3 of 3 parameters describedInitialize a new Git repository at the specified path. Creates a .git directory and sets up the initial branch.
git_log13 of 13 parameters describedView commit history with optional filtering by author, date range, file path, or commit message pattern.
git_merge7 of 7 parameters describedMerge branches together. Integrates changes from another branch into the current branch with optional merge strategies.
git_pull5 of 5 parameters describedPull changes from a remote repository. Fetches and integrates changes into the current branch.
git_push11 of 11 parameters describedPush changes to a remote repository. Uploads local commits to the remote branch.
git_rebase7 of 7 parameters describedRebase commits onto another branch. Reapplies commits on top of another base tip for a cleaner history.
git_reflog3 of 3 parameters describedView the reference logs (reflog) to track when branch tips and other references were updated. Useful for recovering lost commits.
git_remote6 of 6 parameters describedManage remote repositories: list remotes, add new remotes, remove remotes, rename remotes, or get/set remote URLs.
git_reset5 of 5 parameters describedReset current HEAD to specified state. Can be used to unstage files (soft), discard commits (mixed), or discard all changes (hard).
git_set_working_dir3 of 3 parameters describedSet 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_show5 of 5 parameters describedShow details of a git object (commit, tree, blob, or tag). Displays commit information and the diff of changes introduced.
git_stash7 of 7 parameters describedManage stashes: list stashes, save current changes (push), restore changes (pop/apply), or remove stashes (drop/clear).
git_status2 of 2 parameters describedShow the working tree status including staged, unstaged, and untracked files.
git_tag8 of 8 parameters describedManage 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_worktree10 of 10 parameters describedManage multiple working trees: list worktrees, add new worktrees for parallel work, remove worktrees, or move worktrees to new locations.
git_wrapup_instructions2 of 2 parameters describedReturns 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.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.