mcp-git-ingest
Related Servers
Alternatives to mcp-git-ingest
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients to quickly extract GitHub repository summaries, project directory structures, and file contents.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients to quickly extract information from GitHub repositories, including repository summaries, project directory structures, and file contents.-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to analyze GitHub repository structures and read file contents with features like directory traversal, file type analysis, syntax highlighting, and code pattern detection. Supports both public and private repositories through GitHub API integration.8 npmApache 2.0
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients such as Claude Desktop, Cline, and Cursor to quickly extract GitHub repository information, including summaries, directory structure, and file contents.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients to quickly extract GitHub repository summaries, project directory structures, and file content.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients to quickly extract information about GitHub repositories, including repository summaries, project directory structure, and file content.-
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one exposes repository structure, the other reads file contents. There is no realistic overlap in selection, since listing a tree and reading files are separate operations.
Both tools use snake_case and a shared git_ prefix, but the naming pattern is mixed: git_directory_structure is resource-oriented while git_read_important_files is verb-oriented. They remain readable, but the convention is not fully predictable.
Two tools is thin for a repository-ingestion server, even though each tool has a distinct role. The surface is just barely sufficient for basic use, but it sits at the low end of appropriate scope.
The server covers basic cloning, structure discovery, and file reading, but it lacks branch/ref selection, commit metadata, search, and broader file-discovery operations. These are notable gaps for a git-ingestion workflow, though simple use cases can still proceed.