Skip to main content
Glama
skydeckai

MCP GitHub Reader

by skydeckai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to MCP GitHub Reader

No user-submitted related servers found.

    Related Servers

    • github-mcp-server

      ArnabbLank
      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

    • CodeAgent MCP

      saumyajain03
      F
      license
      Not graded
      quality
      C
      maintenance
      A powerful, hosted Model Context Protocol (MCP) server that gives LLMs the ability to understand, navigate, and query any public GitHub repository.
      1
      -

    • Gitingest-MCP

      puravparab
      A
      license
      B
      quality
      D
      maintenance
      An MCP server for gitingest. It allows MCP clients like Claude Desktop, Cursor, Cline etc to quickly extract information about Github repositories including repository summaries, project directory structure, file contents, etc
      3
      135
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    D1.8/5.0

    Scored across 4 tools

    Disambiguation4/5

    The tool names indicate distinct actions: 'analyzeRepository' suggests analysis, 'get_entire_repo_contents' and 'get_individual_file_content' differentiate by scope, and 'searchRepository' is for searching. Without descriptions, the names are clear enough to avoid major confusion.

    Naming Consistency2/5

    The naming convention is inconsistent, mixing camelCase ('analyzeRepository', 'searchRepository') with snake_case ('get_entire_repo_contents', 'get_individual_file_content'). This lack of a consistent pattern makes it harder for agents to predict names.

    Tool Count5/5

    With 4 tools, the set is well-scoped for a 'GitHub Reader' server. Each tool serves a distinct purpose (analysis, full content retrieval, single file retrieval, search) without being overly minimal or bloated.

    Completeness3/5

    The tools cover core reading operations (full content, file content, search), but notable gaps exist, such as retrieving repository metadata (e.g., description, stars) or listing branches. The surface is functional but not comprehensive.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources