git-changelog
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_release_notesA | Generate markdown release notes from git log between optional from/to refs (tags or commits), with conventional-commit grouping. Operates on a local git working tree only (reads history via git log). Does not access remotes or rewrite history. |
| group_conventional_commitsA | List and group commits in a range by conventional type (feat/fix/docs/…). Operates on a local git working tree only (reads history via git log). Does not access remotes or rewrite history. |
| write_changelog_draftA | Write a CHANGELOG.md draft for a version from local git history. Use dryRun to preview. Operates on a local git working tree only (reads history via git log). Does not access remotes or rewrite history. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.