git-changelog
Related Servers
Alternatives to git-changelog
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceTurns raw GitHub commit history into a categorized, human-readable changelog directly inside Claude or any MCP-compatible client.3MIT
- AlicenseBqualityDmaintenanceEnables AI agents to read git commits from local repositories and generate beautifully formatted, categorized changelogs.27 npmMIT
- AlicenseBqualityCmaintenanceGive your AI coding agent superpowers over git history — auto-generate changelogs, analyze commits, attribute blame, and draft release notes via MCP. Zero runtime dependencies.61MIT
- AlicenseNot gradedqualityDmaintenanceGenerate professional changelogs from git history and suggest semver bumps, with optional AI enhancement via Claude.42 npm2MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients such as Claude and Cursor to inspect local git repositories, read recent commits and uncommitted changes, list repos, and draft daily standup updates from that activity.44 npmMIT
- AlicenseAqualityDmaintenanceEnables AI assistants to create conventional Git commits, update changelogs, and optionally push changes to remote repositories.22MIT
TDQS
Scored across 3 tools
There is meaningful overlap: group_conventional_commits, generate_release_notes, and write_changelog_draft all derive output from the same conventional-commit git history. However, the descriptions clarify the intended boundaries: low-level listing, markdown release notes output, and writing a CHANGELOG.md draft.
All tool names follow the same snake_case verb_noun pattern: group_conventional_commits, generate_release_notes, and write_changelog_draft. This is fully predictable and consistent.
Three tools is a well-scoped size for a dedicated git changelog server. Each name corresponds to a distinct output stage, and there is no bloat or unnecessary expansion.
The server covers the core changelog workflow: grouping commits, generating release notes, and writing a draft changelog file. A minor gap is that there is no obvious tool for updating or appending to an existing CHANGELOG.md, but this is not a critical omission for draft-oriented usage.