About git-summary
git-summary is a local Git analysis MCP server for AI coding assistants, producing structured repository overviews, change summaries, and branch checks. It focuses on commit history, code ownership, and repository evolution.
Key features
- 01Repository overviews and commit stats
- 02Semantic summaries for commit ranges
- 03Line-level file ownership analysis
- 04Changelogs grouped by commit type
- 05Branch staleness and ahead/behind checks
- 06Search commit messages and code changes
Use cases
- 01Review contributors and recent commits
- 02Compare changes across versions or branches
- 03Find who changed specific file lines
- 04Create release notes and trace changes
MCP support
The MCP server exposes Git overview, change, blame, branch-health, and history-search tools to clients such as Claude and Cursor.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
6Saved tool list · updated 2w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| repo_path | string | No | Path to the Git repository (defaults to current working directory) |
| commit_count | number | No | Number of recent commits to include (default 20) |
Details
From the project READMEgit-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"
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:
{
"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
- 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
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.