A
licenseA
qualityC
maintenanceEnables 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.
6
MIT
MCP Git Explorer
by jmiedzinski
Related Servers
Alternatives to MCP Git Explorer
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceEnables 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-
- FlicenseNot gradedqualityDmaintenanceEnables Claude to interact with git repositories by providing real-time access to repository status, branch information, commit history, and file changes. Allows users to query their git workspace through natural language commands.-
- FlicenseNot gradedqualityBmaintenanceEnables MCP clients such as Claude Desktop, Cline, and Cursor to extract GitHub repository information, including summaries, directory structure, and file contents.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients such as Claude Desktop, Cline, and Cursor to extract GitHub repository information, including summaries, directory structures, and file contents.-
- FlicenseNot gradedqualityDmaintenanceEnables to interact with GitHub repositories directly from Claude, supporting actions like viewing repos, checking status, committing and pushing changes, and managing pull requests.-
TDQS
A4.2/5.0
Scored across 4 tools
Disambiguation4/5
The tools are mostly distinct: get_codebase returns full content, estimate_codebase returns statistics, get_file retrieves a single file, and check_gitlab_token_status checks configuration. There is minor overlap between get_codebase and estimate_codebase (both analyze the repo), but their outputs are clearly different.
Naming Consistency5/5
All tool names follow the verb_noun pattern in snake_case (get_, check_, estimate_). The naming is consistent and predictable, with no mixed conventions.
Tool Count5/5
Four tools is well-suited for a Git explorer. The scope is focused on repository inspection, and each tool serves a distinct purpose without bloat or excessive overlap.
Completeness4/5
The tool set covers the core needs: full codebase extraction, single file retrieval, and statistics. A minor gap is the lack of a dedicated tool for listing the repository tree without content, though estimate_codebase partially addresses this. Overall, it is reasonably complete for its stated purpose.