MCP.Market

Git Summary MCP server

by yifanyifan897645·io.github.yifanyifan897645/git-summary·v0.1.2

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

B82/100grade B
What users say
No reviews yet
Be the first
Safety scan
B82/100

full report

Adoption
New

0 stars63 downloads/wk

Reviews

Write one

Nobody has reviewed Git Summary yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Git Summary tools (6)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • git_blame

    Analyze who wrote each line of a file, when, and in which commit. Get top contributors and ownership breakdown. Optionally limit to a line range.

  • git_branch_health

    Analyze all local branches: find stale branches, merged branches ready for cleanup, and branches that are ahead/behind. Helps keep your repo tidy.

  • git_changelog

    Auto-generate a changelog from Git commits. Groups commits by type (feat, fix, docs, etc.) using conventional commit format. Specify a range or get the full log.

  • git_changes

    Get a summary of changes in a commit range: what files changed, who changed them, and a diff stat. Useful for understanding what happened between two points in history.

  • git_search

    Search through Git history for commits matching a query. Searches both commit messages and code changes (pickaxe search). Find when a change was introduced or a bug was created.

  • git_summary

    Get a structured overview of a Git repository: current branch, recent commits, contributors, and repo stats. Works on any local Git repo.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan5 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 167 days ago8/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 82/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Git Summary compares

Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
82/100
higher than 60% of 1,119 Developer tools servers
Tools
6
the typical Developer tools server has 7
Tools that change things
0%
typical: 5%. Fewer write tools means less an agent can break
Downloads a week
63
more than 46% of 436 Developer tools servers with a package

What its tools let an agent do: 6 read

Install Git Summary in Claude Code, Cursor or VS Code

Runs npx -y git-summary-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add git-summary -- npx -y git-summary-mcp
Add to Cursor

What the publisher says

From the Git Summary repository's README, as published. We do not edit it. Read it on GitHub

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

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"

gitbranchhealth

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:

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

Cursor

Add to .cursor/mcp.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 →

  • webcheck-mcp — Website health analysis
  • git-summary-mcp — Git repository intelligence
  • mcp-checkup — MCP setup health analyzer
  • dev-utils-mcp — Developer utilities
  • codescan-mcp — Codebase health scanner
  • deadlink-checker-mcp — Dead link detector

License

MIT

Nothing above is checked by us. What we check is on the safety report.

Git Summary: common questions

Is Git Summary MCP server safe?
Mostly: it is graded B (82/100). Read the Git Summary safety report
How do I install Git Summary?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Git Summary need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Git Summary maintained?
The last commit was 205 days ago (2026-04-13). The latest release is v0.1.2.
What can I use instead of Git Summary?
Servers from other publishers that do the same job: Repowise MCP server, SoloMD MCP server and argot MCP server.
How does Git Summary compare with other Developer tools MCP servers?
safety score 82/100 (higher than 60% of 1,119 Developer tools servers); tools 6 (the typical Developer tools server has 7); tools that change things 0% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Git Summary

Same job from other publishers: the closest match first, then the best rated.

  • Repowise
    Codebase intelligence for AI coding agents — graph, git history, docs, decisions, code health.
    B
  • SoloMD
    Read and search a folder of Markdown notes: search, backlinks, tags, tasks, outlines, git history.
    B
  • argot
    Read-only context and complete checks against patterns learned from git history. Local; no LLM.
    B
  • Srclight
    Deep code indexing for AI agents. FTS5 + embeddings + call graphs + git intelligence. Fully local.
    A
  • Nexusmem
    Local-first memory for AI coding agents: shell history with exit codes, git diffs, docs, MCP.
    A

More from yifanyifan897645 →