git-changelog-mcp
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| git_get_recent_commitsA | Fetch the most recent commits from a local git repository. Returns structured commit objects that can be passed directly to git_generate_markdown_changelog. |
| git_generate_markdown_changelog | Format a list of commit objects into a structured Markdown changelog grouped into Features, Fixes, and Chores. |
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 1 tool
With only one tool, there is no possibility of confusion; the tool's purpose is clearly distinct.
The single tool name follows a consistent verb_noun pattern with underscores, which would be consistent if more tools existed.
One tool is too few for a changelog server; it only fetches commits and lacks the essential changelog generation tool, making the server appear incomplete.
The server only provides half of the changelog workflow (fetching commits) and is missing the companion tool to generate changelogs, resulting in a dead end.