Skip to main content
Glama
puravparab

Gitingest-MCP

by puravparab

Related Servers

Alternatives to Gitingest-MCP

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      An MCP server that wraps gitingest to enable Claude Code to analyze GitHub repositories, providing access to code structures, statistics, and full content. It facilitates the creation of structured study notes and supports both public and private repositories through the Model Context Protocol.
      1
      -
    • A
      license
      B
      quality
      D
      maintenance
      A minimal MCP server for GitHub that enables browsing repos, reading code, searching, and getting insights through natural language via Claude, Cursor, or any MCP client.
      7
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A read-only MCP server that exposes GitHub user profiles, repository info, and search via tools for AI assistants like Claude.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives Claude Desktop complete intelligence about any public GitHub repository. Research libraries, compare packages, audit dependencies, and explore codebases through natural conversation.
      1
      MIT

    TDQS

    B3.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: git_files retrieves specific file contents, git_summary provides a high-level repository overview with metrics, and git_tree returns the repository's file/directory structure. There is no overlap in functionality - an agent can easily distinguish between getting file contents, getting structural information, or getting a summary.

    Naming Consistency5/5

    All three tools follow a perfect 'git_' prefix pattern with descriptive suffixes (files, summary, tree). The naming is completely consistent in style, format, and verb usage, making the tool set immediately understandable and predictable.

    Tool Count3/5

    With only 3 tools, this feels somewhat thin for a GitHub ingestion server. While the tools cover basic repository inspection (files, structure, summary), there are likely additional ingestion operations that would be useful, such as commit history retrieval, branch listing, or contributor information. The count is borderline minimal for the apparent scope.

    Completeness3/5

    The tool set covers fundamental repository inspection operations but has notable gaps for a comprehensive ingestion system. Missing are tools for retrieving commit history, branch information, contributor data, or issue tracking. While the existing tools provide a foundation, agents will encounter dead ends when needing more complete repository metadata beyond file content and structure.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues