Git Summary

io.github.yifanyifan897645Published by GitHub account yifanyifan897645v0.1.2Updated Oct 24, 2026

Git repo intelligence: summaries, blame, changelogs, branch health, and history search

VerifiedSTDIODesktop onlyDeveloper ToolsData & Analytics

Overview

AI-generated overview

Lets an assistant read and summarize a local Git repository: overviews, change summaries, blame, branch health, and history search.

What you can do
Provides five read-oriented tools over a local Git repository. git_summary gives a structured overview of the current branch, recent commits, contributors, and stats. git_changes summarizes what changed across a commit range, including files, authors, and diff stats. git_blame reports line ownership and contributor breakdowns, git_branch_health finds stale, merged, and ahead/behind branches, and git_search looks through commit messages and code changes to find when something was introduced or modified.
When to use it
Useful when an assistant needs project history rather than just current file contents: generating changelogs or release notes, preparing code reviews, tracing when a bug or config value changed, or finding branches that can be cleaned up. It is aimed at local repositories on a developer machine.
Requirements
Runs locally over stdio, typically started with npx from the npm package git-summary-mcp. Needs Node.js 18 or later and Git installed and available in PATH, and must be run inside or pointed at a Git repository. No accounts, API keys, or environment variables are declared.
Before you install
The tools read repository data, including commit history, authorship, and code changes, and pass it to the assistant, so private or sensitive repository content may leave the local machine depending on the client. It is desktop-only and not available as a web executable. No credentials, payments, or write operations are declared.

Installation

In SourceWeft

  1. Open Git Summary 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

git-summary-mcp

An MCP server that gives AI assistants deep understanding of your local Git repositories. Get instant repo overviews, semantic change summaries, blame analysis, auto-generated changelogs, branch health checks, and history search — all from within Claude, Cursor, or any MCP client.

Quick Start

bash
npx git-summary-mcp

Zero config. No API keys. No accounts. Just run it in any Git repository.

Tools

git_summary

Structured overview of a repository: current branch, recent commits, contributors, and stats.

"Summarize this repository""Who are the top contributors?""Show me the last 10 commits"

git_changes

Semantic change summary for any commit range. See what files changed, who changed them, and the overall diff stat.

"What changed between v1.0 and v2.0?""Summarize the changes in the last week""What did the feature branch change?"

git_blame

Analyze file ownership: who wrote each line, when, and in which commit. Get contributor breakdowns.

"Who last modified src/index.ts?""Show me the blame for lines 50-100 of app.py""Who owns most of this file?"

git_changelog

Auto-generate a changelog grouped by commit type (features, fixes, docs, etc.) using conventional commit detection.

"Generate a changelog for the last release""Create release notes from v1.0 to v2.0"

git_branch_health

Find stale branches, merged branches ready for cleanup, and branches that are ahead/behind.

"Which branches are stale?""Any branches that have been merged and can be deleted?""Show me branch health"

git_search

Search through commit messages and code changes (pickaxe search) to find when something was introduced or changed.

"When was the login function added?""Find commits that mention 'authentication'""When was this config value changed?"

Installation

Claude Desktop / Claude Code

Add to your MCP config:

json
{  "mcpServers": {    "git-summary": {      "command": "npx",      "args": ["-y", "git-summary-mcp"]    }  }}

Cursor

Add to .cursor/mcp.json:

json
{  "mcpServers": {    "git-summary": {      "command": "npx",      "args": ["-y", "git-summary-mcp"]    }  }}

Windsurf

Add to your MCP configuration with the same format as above.

Why?

AI coding assistants can read files and run commands, but they don't inherently understand your project's history. This MCP server gives them structured, token-efficient Git intelligence so they can:

  • Understand who worked on what and when
  • Generate accurate changelogs and release notes
  • Find when bugs were introduced
  • Identify stale branches and cleanup opportunities
  • Summarize changes for code reviews and PRs

Requirements

  • Node.js 18+
  • Git installed and available in PATH
  • Must be run inside (or pointed at) a Git repository

Part of the MCP Toolkit

View all servers →

License

MIT

Source: README.md at commit efd43e3

Tools

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

Version history

1
  1. v0.1.2LatestSep 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