git-mcp-server

Stage files for commit. Add file contents to the staging area (index) to prepare for the next commit.

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.

Manage branches: list all branches, show current branch, create a new branch, delete a branch, or rename a 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.

Switch branches or restore working tree files. Can checkout an existing branch, create a new branch, or restore specific files.

Cherry-pick commits from other branches. Apply specific commits to the current branch without merging entire branches.

Remove untracked files from the working directory. Requires force flag for safety. Use dry-run to preview files that would be removed.

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.

Clone a repository from a remote URL to a local path. Supports HTTP/HTTPS and SSH URLs, with optional shallow cloning.

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.

View differences between commits, branches, or working tree. Shows changes in unified diff format.

Fetch updates from a remote repository. Downloads objects and refs without merging them.

Initialize a new Git repository at the specified path. Creates a .git directory and sets up the initial branch.

View commit history with optional filtering by author, date range, file path, or commit message pattern.

Merge branches together. Integrates changes from another branch into the current branch with optional merge strategies.

Pull changes from a remote repository. Fetches and integrates changes into the current branch.

Push changes to a remote repository. Uploads local commits to the remote branch.

Rebase commits onto another branch. Reapplies commits on top of another base tip for a cleaner history.

View the reference logs (reflog) to track when branch tips and other references were updated. Useful for recovering lost commits.

Manage remote repositories: list remotes, add new remotes, remove remotes, rename remotes, or get/set remote URLs.

Reset current HEAD to specified state. Can be used to unstage files (soft), discard commits (mixed), or discard all changes (hard).

Set the session working directory for all git operations. This allows subsequent git commands to omit the path parameter and use this directory as the default.

Show details of a git object (commit, tree, blob, or tag). Displays commit information and the diff of changes introduced.

Manage stashes: list stashes, save current changes (push), restore changes (pop/apply), or remove stashes (drop/clear).

Show the working tree status including staged, unstaged, and untracked files.

Manage tags: list all tags, create a new tag, or delete a tag. Tags are used to mark specific points in history (releases, milestones).

Manage multiple working trees: list worktrees, add new worktrees for parallel work, remove worktrees, or move worktrees to new locations.

Provides the user's desired Git wrap-up workflow and instructions. Returns custom workflow steps (if configured) or default best practices for reviewing, documenting, and committing changes. Includes current repository status to guide next actions.