Git

io.github.rog0xPublished by GitHub account rog0xv1.0.1Updated Oct 24, 2026

Git log, diff, blame, branch stats for AI agents

VerifiedSTDIODesktop onlyDeveloper ToolsData & Analytics

Overview

AI-generated overview

A local MCP server that lets an AI assistant inspect Git repositories: commit history, diffs, blame, branch status and activity statistics.

What you can do
Read commit history with filters by author, date range and file path, and compare refs with structured diff summaries or stats only. Show line-by-line authorship of a file, optionally for a line range or a specific commit. Summarize repository activity: commit counts, top contributors, most-changed files and trends over time. List branches with last commit info, ahead/behind counts and merged or unmerged status.
When to use it
Useful when you want an assistant to reason about a local repository's history, review what changed between branches or commits, find who last touched specific lines, or get a quick activity overview without calling a hosting API.
Requirements
Runs as a local process over stdio from the npm package @rog0x/mcp-git-tools. Needs Node.js 18 or later and Git installed and available on PATH. Each tool call requires an absolute path to the repository. No authentication, API keys or environment variables are declared.
Before you install
The tools read local repositories, so the assistant can see commit history, file contents in diffs and blame, and author names and emails. Point it only at repositories you are comfortable exposing to the model. The README lists only read-style analysis tools; no write, push or delete operations are described.

Installation

In SourceWeft

  1. Open Git in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

mcp-git-tools

Git repository analysis tools for AI agents, served over MCP (Model Context Protocol). Analyzes local repositories using native git commands — no GitHub API required.

Tools

ToolDescription
git_logGet commit history with filtering by author, date range, and file path
git_diffShow diff between commits, branches, or tags with change summaries
git_blameShow who last modified each line of a file with commit info
git_statsRepository statistics: commits, contributors, activity over time, most changed files
git_branchList branches with last commit info, ahead/behind counts, merged/unmerged status

Prerequisites

  • Node.js >= 18
  • Git installed and available in PATH

Setup

bash
npm installnpm run build

Configuration

Add to your MCP client configuration:

json
{  "mcpServers": {    "git-tools": {      "command": "node",      "args": ["D:/products/mcp-servers/mcp-git-tools/dist/index.js"]    }  }}

Tool Details

git_log

Retrieve recent commit history with optional filters.

Parameters:

  • repoPath (required) — Absolute path to the Git repository
  • count — Number of commits to return (default: 20)
  • author — Filter by author name or email
  • since / until — Date range filters
  • path — Filter to commits touching a specific file or directory

git_diff

Compare two refs and get a structured summary of changes.

Parameters:

  • repoPath (required) — Absolute path to the Git repository
  • from — Start ref (default: HEAD~1)
  • to — End ref (default: HEAD)
  • path — Limit diff to a specific file or directory
  • summaryOnly — Return only stats without full diff text

git_blame

See line-by-line authorship of a file.

Parameters:

  • repoPath (required) — Absolute path to the Git repository
  • filePath (required) — File path relative to repo root
  • startLine / endLine — Blame a specific line range
  • ref — Blame at a specific commit

git_stats

Get a high-level overview of repository activity.

Parameters:

  • repoPath (required) — Absolute path to the Git repository
  • topAuthors — Number of top contributors to list (default: 10)
  • topFiles — Number of most-changed files to list (default: 10)

git_branch

List and analyze branches.

Parameters:

  • repoPath (required) — Absolute path to the Git repository
  • baseBranch — Branch to compare against (default: main or master)
  • includeRemote — Include remote-tracking branches
  • mergedOnly / unmergedOnly — Filter by merge status

License

MIT

Source: README.md at commit d7330b0

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts