Git Metrics MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GIT_TIMEOUT | No | Set GIT_TIMEOUT env var (default: 30s) | 30 |
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 |
|---|---|
| health_checkA | Verify server is operational |
| get_commit_statsC | Get commit statistics for a repository |
| get_author_metricsC | Get detailed metrics per author |
| get_file_churnB | Get files with most changes (churn) |
| get_team_summaryC | Get comprehensive team performance summary |
| get_commit_patternsC | Analyze commit frequency patterns by day and hour |
| get_code_ownershipC | Analyze code ownership and bus factor |
| get_velocity_trendsC | Track velocity trends over time |
| get_collaboration_metricsC | Analyze team collaboration patterns |
| get_quality_metricsC | Code quality indicators (commit size, reverts, etc) |
| get_technical_debtC | Identify technical debt indicators |
| get_conventional_commitsC | Analyze conventional commit usage and release patterns |
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 12 tools
Each tool targets a distinct metrics category (author, ownership, collaboration, commits, quality, etc.), with no functional overlap. Descriptions clearly differentiate them.
All tools use a consistent 'get_' prefix followed by a descriptive noun phrase, except 'health_check' which omits the prefix. This minor deviation lowers the score slightly.
12 tools cover a well-scoped metrics domain without being excessive or insufficient. Each tool provides meaningful and distinct functionality.
The set covers a broad range of git metrics (author, commits, collaboration, quality, technical debt). Minor gaps exist, such as missing PR or issue metrics, but overall it's fairly comprehensive.