git-log-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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| git_logA | Use this tool to investigate when a code/configuration change happened and infer why it happened from commit history. Choose it when you need commit timelines, authorship context, or intent signals from commit messages and diffs for a specific module or identifier. It is not for repository file content reads or branch manipulation; it is for history analysis and change attribution. |
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 a single tool, there is no possibility of confusion between tools. The description explicitly distinguishes it from file reads and branch manipulation, making its purpose clear.
The single tool name `git_log` follows a clean, conventional snake_case pattern that aligns with the server's purpose. Consistency is trivially maintained with one tool.
One tool is slightly under the typical 3-15 range, but for a narrowly scoped git-log server, it is reasonable and not excessive. The tool's flexibility helps compensate for the thin count.
The tool covers the core need of commit history analysis and change attribution, including messages and diffs. Minor gaps exist for operations like blame or range-specific logs, but the description implies the tool can handle broad historical queries.