Git

What git MCP server does

The git MCP server gives AI agents structured access to analysis of local Git repositories. It covers five common inspection tasks: commit history, comparisons between Git references, line-level authorship, repository activity statistics, and branch status. The tools operate on repositories available on the machine running the MCP process rather than on a hosted Git service.

Use git_log to inspect commits and optionally filter them by author, date range, or file path. git_diff compares two commits, branches, or tags and can return either change details or a summary of the change statistics. git_blame reports the commit and author associated with each line, including an optional line range or historical reference.

git_stats summarizes repository activity, including commit and contributor information, activity over time, and frequently changed files. git_branch reports branch information such as the latest commit, ahead or behind counts, and merge status. It can also include remote-tracking branches.

How it works

The git MCP server uses native Git commands and communicates with an MCP client over its configured process. Each request supplies a repository location, and the server performs the corresponding Git inspection operation there. Most tools require repoPath as an absolute path; git_blame additionally requires a file path relative to the repository root.

The tools provide defaults for common queries. Log requests return 20 commits unless another count is supplied. Diffs compare HEAD~1 with HEAD by default. Statistics list 10 top contributors and 10 most-changed files by default. Branch comparisons use main or master as the default base when available.

Setup and configuration

Running this git MCP server requires Node.js 18 or newer and Git installed and available through PATH. From the repository checkout, install dependencies and build the project:

npm install
npm run build

Register the generated Node.js entry point in the MCP client configuration. The command uses the built dist/index.js file, with its path changed to match the local checkout:

{
  "mcpServers": {
    "git-tools": {
      "command": "node",
      "args": ["/path/to/mcp-git-tools/dist/index.js"]
    }
  }
}

Tools and capabilities

• git_log: returns commit history with author, date, count, and path filters.
• git_diff: compares refs, optionally limits the comparison to a path, and supports summary-only output.
• git_blame: returns line-by-line authorship for a file, a selected range, or a specified ref.
• git_stats: reports commits, contributors, activity over time, and commonly changed files.
• git_branch: lists branches with last-commit details, ahead or behind counts, and merged or unmerged filtering.

Limitations and notes

The git MCP server analyzes local repositories and does not require the GitHub API. The provided tools are for repository inspection; the material does not describe commands for editing files, creating commits, switching branches, or pushing changes. Repository paths must be accessible to the host process, and Git must be installed correctly for requests to work.