F
licenseNot graded
qualityC
maintenanceA lightweight MCP server that analyzes Git repository history and provides insights through AI-compatible tools. It supports hotspot detection, contributor analysis, and code churn tracking.
-
mcp-git-historian
Related Servers
Alternatives to mcp-git-historian
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceA local Git intelligence MCP server that provides deep repository analytics including hotspots, churn, knowledge maps, and risk scoring, all computed from commit history without data leaving your machine.12MIT
- FlicenseNot gradedqualityCmaintenanceThis MCP server provides a tool to analyze git repository hotspots, returning a sorted list of files with risk scores based on change frequency and author count.-
- AlicenseAqualityCmaintenanceA local-only MCP server for understanding Git repositories, offering repository summary, recent changes, file hotspots, and hygiene checks without network access.4121 npmMIT
- FlicenseNot gradedqualityDmaintenanceA local-only MCP server that exposes git repository history, diffs, and status as tools for LLM clients, working entirely against a local git repo on disk.-
- FlicenseNot gradedqualityCmaintenanceMCP server that analyzes git activity from a repository mounted at /repo, exposing an SSE interface and health check endpoint.-
TDQS
A3.9/5.0
Scored across 11 tools
Disambiguation5/5
Each tool targets a distinct git-history analysis: bus_factor for commit concentration, hotspots for churn, blame_summary for line ownership, etc. The descriptions explicitly clarify boundaries (e.g., bus_factor notes 'For line-level ownership and inactive authors use knowledge_risk'). health_report is an aggregator but is clearly marked as a combined overview, not a replacement.
Naming Consistency3/5
Mostly snake_case but mixed conventions: bus_factor and repo_summary are noun phrases, while search_commits and find_change are verb phrases. The pattern is not strictly consistent, though readable and domain-appropriate.
Tool Count5/5
11 tools for a git historian server is well-scoped, covering key analysis dimensions (bus factor, hotspots, coupling, ownership, etc.) without redundancy. The inclusion of health_report as an aggregator is justified for quick overviews.
Completeness4/5
Comprehensive for historical analysis but lacks tools for comparing branches or examining uncommitted changes (e.g., diff, status), which are common in git toolkits. Minor gap, but core forensic and health workflows are well-covered.
Maintenance
ActivityMaintained
ResponsivenessNo issues