🔍 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.

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 (not yet on PyPI — install from source)
git clone https://github.com/ManiaSacha/gitlog-mcp.git
cd gitlog-mcp
pip install -e .

# 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)

pip install gitlog-mcp will work once this is published to PyPI. Until then, install from source as shown above. There's a real, tested publish pipeline ready to go (tag-triggered, PyPI Trusted Publishing) — see RELEASING.md for the full process.

Claude Code config

{
  "mcpServers": {
    "gitlog": {
      "command": "gitlog-mcp",
      "args": ["--repo", "."]
    }
  }
}

Cursor config (.cursor/mcp.json)

{
  "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.0 and v1.3.0."

"Who introduced this buggy line in src/parser.py and why?"

"Draft release notes for the next version based on recent commits."

Tools exposed

Architecture

gitlog-mcp (single file, ~250 lines)
├── FastMCP server (stdio transport)
├── GitRunner — thin wrapper over `git` CLI
└── Tools — each maps to a git subcommand + parsing

Deliberately 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

• --repo auto-detection from cwd
• Structured 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. ⭐