ShadowGit MCP Server
Related Servers
Alternatives to ShadowGit MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables AI assistants to perform code reviews by providing access to staged files, git diffs, and repository file content. It allows users to evaluate changes and context within any local git repository before committing or pushing.31 npmISC
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to access live GitHub repository data without cloning, supporting repo summarization, file explanation, recent changes, and dependency analysis.MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to search and inspect code repositories, manage issues and pull requests, and analyze user contributions.13MIT
- AlicenseBqualityDmaintenanceEnables AI assistants to inspect local Git repositories and interact with the GitHub API for reading commits, diffs, files, issues, comments, pull requests, and project boards.10158 npmISC
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants like Claude to navigate git repository history, providing insights into code evolution and helping understand legacy systems.MIT
- AlicenseAqualityBmaintenanceConnects AI assistants to GitHub repositories, pull requests, issues, commits, and code search while enabling repository visibility controls, CI/CD monitoring, sandboxed local filesystem access, and code quality/security analysis.131MIT
TDQS
Scored across 9 tools
Most tools target clearly distinct actions: sessions, checkpoints, repository listing, raw git reads, map/context reads, and lens read/write. The main overlap is conceptual: get_map, get_code_context, and get_lens all expose map/dependency/rule information, though their descriptions distinguish project-level, symbol-level, and snapshot-range views.
Seven of nine tools follow a readable snake_case action_noun pattern: list_repos, start_session, end_session, get_map, get_code_context, get_lens, and write_lens_words. The bare nouns/verbs checkpoint and git_command are minor deviations from that pattern.
Nine tools is well within the typical 3-15 range and fits the server's multi-part scope: repository listing, sessions, checkpoints, raw history queries, code-map context, and Lens reading/writing. Each tool appears to earn its place without obvious filler.
The core lifecycle is covered: list projects, start/end sessions, create checkpoints, inspect history via read-only git commands, read map/context/Lens data, and write Lens words. Minor gaps exist around project administration and direct rule authoring, but those may be intentionally outside the server's scope.