F
licenseB
qualityD
maintenanceEnables analysis and querying of Git repository content (both public and private) through a unified tool that provides repository summaries, file structures, and full content optimized for LLM consumption.
1
-
Repository Analyzer MCP Server
by DocNR
Related Servers
Alternatives to Repository Analyzer MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables Claude to inspect, analyze, and grade local Git repositories with tools for stats, TODO scanning, git history, large file detection, health scores, and tech stack fingerprinting.6MIT
- FlicenseNot gradedqualityCmaintenanceProvides GitHub repository analysis tools for Claude, including repo summaries, commit history, issue tracking, contributor stats, and code quality assessment. Enables natural language queries about code quality, contributor activity, and repository comparisons.-
- FlicenseNot gradedqualityCmaintenanceEnables natural language analysis of local software repositories, providing insights into project structure, technologies, code, tests, and Git history through MCP tools.-
- FlicenseBqualityDmaintenanceProvides comprehensive Git repository insights including author statistics, branch health, and code churn analysis. It enables users to perform data-driven assessments of their codebase and track development patterns through the Model Context Protocol.3-
- FlicenseNot gradedqualityDmaintenanceAnalyzes local Git repositories to provide detailed insights into commit statistics, contributor activity, and frequently changed files. It allows users to query repository history and access structured activity data through the Model Context Protocol.-
TDQS
D1.5/5.0
Scored across 8 tools
Disambiguation2/5
Multiple tools share the 'analyze-' prefix with no descriptions, making it impossible for an agent to distinguish between targets like code, ndk, repo, etc. Some tools like debug-path and git-history have unique names but lack descriptions, still causing ambiguity.
Naming Consistency2/5
The naming convention is mixed: most tools use 'analyze-<subject>' but three diverge with different verbs (debug, git, search). This inconsistency disrupts predictability.
Tool Count4/5
With 8 tools, the count is reasonable for a repository analysis server. It covers several analysis facets without being overwhelming.
Completeness2/5
The tool surface appears focused on analysis but lacks operations for managing results, listing analyses, or performing updates. Without descriptions, it's unclear if core workflows are supported.
Maintenance
ActivityInactive
ResponsivenessNo issues