git-context-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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| project_statusC | Returns a technical snapshot of a local git repository. |
| recent_activityC | Analyzes recent git history to find 'hot' files. |
| work_summaryC | Summarizes development progress and technical debt. |
| code_mapC | Generates a file tree and identifies key architectural files. |
| risk_scanC | Identifies risky areas (hotspots) in the codebase. |
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 5 tools
Each tool describes a distinct analysis aspect: code map, project status, recent activity, risk scan, and work summary. There is slight overlap between 'recent_activity' and 'risk_scan' both mentioning 'hot' files, but the descriptions are clear enough to differentiate.
All tool names follow a consistent pattern: two words in snake_case with a noun or adjective followed by a noun (e.g., code_map, project_status). No mixing of styles.
With 5 tools, the set is well-scoped for a git analysis server. Each tool serves a distinct purpose without being too few or too many.
The tools cover high-level analyses like structure, status, recent changes, risk, and progress, but lack lower-level git operations (e.g., commit details, branch info, diffs). This is a minor gap for a comprehensive git context server.