git-graph
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GIT_GRAPH_REPO | No | Absolute path to the target Git repository. Set explicitly when the client does not launch the server from the target repository. |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| git_historyB | Show a graph of local commits and branches. Does not modify the repository or contact remotes. |
| git_commitB | Read commit metadata, file statistics, and a bounded patch for a full Git hash. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| git-graph |
TDQS
Scored across 2 tools
git_history shows a graph overview of commits and branches, while git_commit retrieves detailed metadata and patch for a specific hash. The two purposes are clearly different, though both operate on commit history and could be slightly confused by an agent skimming descriptions.
Both tools follow a consistent `git_` prefix with snake_case nouns: `git_history` and `git_commit`. The pattern is predictable and readable, with no mixed conventions.
Two tools is thin for a server focused on Git graph exploration, sitting at the borderline identified in the calibration. Additional tools for branch listing, searching, or diffing would make the set feel more complete without being excessive.
The server covers viewing the commit graph and inspecting a specific commit, but notable read-only operations are missing: branch/tag listing, searching or filtering history, file-level history, and showing diffs between arbitrary commits. These gaps limit deeper Git exploration workflows.