gitlog-mcp
Provides tools for analyzing git history, including changelog generation, commit analysis, blame attribution, release notes drafting, and repo health summaries.
š gitlog-mcp
Give your AI coding agent superpowers over git history.
gitlog-mcp is a Model Context Protocol (MCP) server that lets AI agents (Claude Code, Cursor, Windsurf, and any MCP client) understand what changed in a repository ā auto-generate changelogs, analyze commits, attribute blame, and draft release notes.
"What changed in this repo?" is the question every AI agent gets wrong. This fixes it.
Why this exists
AI coding agents are great at writing code but famously bad at knowing the history of a codebase. They hallucinate changelogs, misattribute blame, and guess at release notes. gitlog-mcp gives them a reliable, structured window into git log ā so their answers are grounded in what actually happened, not invented.
Related MCP server: Continuum
Features
š Auto-changelog ā generate a clean, grouped changelog from any tag/commit range
š Commit analysis ā explain why a change happened, not just what changed
š¤ Blame attribution ā who touched what, and when (with context)
š·ļø Release notes ā draft release notes from tag-to-tag diffs
š Repo health ā commit frequency, top contributors, churn hotspots
š§± Zero runtime dependencies ā pure Python stdlib + the MCP SDK, one file
Quick start
# 1. Install from PyPI
pip install gitlog-mcp
# 2. Run standalone (for testing) ā defaults to the current directory
gitlog-mcp
gitlog-mcp --repo /path/to/your/repo
# 3. Or add directly to your agent's MCP config (see below)Want the local web dashboard too? It's an optional extra, not installed by default:
pip install "gitlog-mcp[ui]". Plainpip install gitlog-mcpstays exactly as dependency-free as ever.
Installing from source (for contributors):
git clone https://github.com/ManiaSacha/gitlog-mcp.git && cd gitlog-mcp && pip install -e .ā see CONTRIBUTING.md for details.
Claude Code config
{
"mcpServers": {
"gitlog": {
"command": "gitlog-mcp",
"args": ["--repo", "."]
}
}
}Cursor config (.cursor/mcp.json)
{
"mcpServers": {
"gitlog": {
"command": "gitlog-mcp",
"args": ["--repo", "."]
}
}
}Windsurf config
{
"mcpServers": {
"gitlog": {
"command": "gitlog-mcp",
"args": ["--repo", "."]
}
}
}Debug it standalone
Want to poke at the tools directly before wiring up an agent? The MCP Inspector gives you a UI to call each tool by hand:
npx @modelcontextprotocol/inspector gitlog-mcp --repo .Example agent prompts
"Generate a changelog of everything that changed between
v1.2.0andv1.3.0."
"Who introduced this buggy line in
src/parser.pyand why?"
"Draft release notes for the next version based on recent commits."
Tools exposed
Tool | Description |
| Grouped changelog for a commit/tag range |
| Explain a specific commit's intent and impact |
| Line-level attribution for a file |
| Draft release notes between two tags |
| Contributor + churn summary |
| Find commits by message/author/date |
Web dashboard (optional)
Prefer a browser to a terminal? gitlog-mcp-ui serves a small local dashboard on top of the same git-reading code the MCP tools use ā same data, human-readable.
pip install "gitlog-mcp[ui]"
gitlog-mcp-ui --repo /path/to/repoThis prints a URL (http://127.0.0.1:8765 by default) ā open it in your browser; it won't open one for you.
View | What it shows |
Changelog | Commit range picker ( |
Repo Health | Contributor stats, commit totals |
Blame | Per-file, per-line attribution |
Read-only ā no write actions anywhere. Local-only by construction: binds to 127.0.0.1 only (there's no --host flag, so it can't be exposed to the network even by accident), and validates every request's Host header too, closing the DNS-rebinding gap a loopback bind alone doesn't cover. No auth needed, because nothing but your own machine can reach it.
It's an optional extra (pip install gitlog-mcp[ui]), not installed by default. The core gitlog-mcp server has zero runtime dependencies beyond the MCP SDK, full stop ā the dashboard doesn't change that. It's http.server from the stdlib, no framework, no extra deps of its own.
Architecture
gitlog-mcp (single file, ~300 lines)
āāā FastMCP server (stdio transport)
āāā GitRunner ā thin wrapper over `git` CLI
āāā Tools ā each maps to a git subcommand + parsingDeliberately small. You can read the whole thing in an afternoon ā that's a feature.
Contributing
PRs welcome. Small, focused, well-tested changes only. See CONTRIBUTING.md.
Release process and versioning are documented in RELEASING.md.
Roadmap
--repoauto-detection from cwdStructured JSON output for all tools
GitHub/GitLab remote integration
Tests + CI badge
License
MIT Ā© 2026 ā built in the open, for the open-source community.
Star this repo if you want AI agents to stop hallucinating your changelog. ā
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityDmaintenanceAI-powered Git workflow intelligence ā 10 tools for commit messages, branch naming, PR descriptions, changelogs, and stream-based context management. Works with Cursor, Claude Desktop, Windsurf, VS Code, and all MCP clients.MIT
- Alicense-qualityDmaintenanceAutomatically extracts architectural decisions, patterns, and insights from Git commits to build a local, structured project memory. It exposes this living context to AI tools via MCP, allowing them to understand the historical reasoning and evolution behind your codebase.417MIT
- AlicenseAqualityCmaintenanceSemantic git queries via MCP. Beyond git log ā answer who/what/why about any line, file, or branch with blame, co-change, PR linkage.6192MIT
- AlicenseBqualityCmaintenanceEnables AI agents to read git commits from local repositories and generate beautifully formatted, categorized changelogs.25MIT
Related MCP Connectors
Repo intel for AI coding agents: overview, PRs, contributors, hot files, CI, deps. Remote MCP.
Package intelligence MCP for AI agents ā 22 tools, 19 ecosystems, AGPL SDK, free.
A Model Context Protocol (MCP) application for automated GitHub PR analysis and issue management.ā¦
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ManiaSacha/gitlog-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server