Skip to main content
Glama
tuanle96

GitHub MCP Server

by tuanle96
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to GitHub MCP Server

No user-submitted related servers found.

    Related Servers

    • GitHub MCP Server

      AlexKissiJr
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables comprehensive interaction with the GitHub API, including file operations, repository management, issue tracking, pull request workflows, and advanced search functionality across code, issues, and users.
      88,163 npm
      MIT

    • GitHub MCP Server

      asbloom-py
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with GitHub through the GitHub API, supporting file operations, repository management, advanced search, and issue tracking with comprehensive error handling and automatic branch creation.
      379 npm
      1
      ISC

    • GitHub MCP Server

      awaybreaktoday
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables comprehensive interaction with GitHub repositories, including code management, issues, pull requests, and full GitHub Actions workflow control with triggering, monitoring, and artifact management capabilities.
      64 npm
      -
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    B3.2/5.0

    Scored across 47 tools

    Disambiguation4/5

    Most tools have distinct purposes targeting specific GitHub resources and actions, such as add_card_to_column vs. move_card. However, some overlap exists between project-related tools (e.g., create_project vs. create_project_v2) and search tools (search_code, search_issues, search_repositories, search_users), which could cause minor confusion. Descriptions help clarify, but the sheer number of tools increases cognitive load.

    Naming Consistency5/5

    Tool names follow a highly consistent verb_noun pattern throughout, such as create_issue, get_file_contents, and list_pull_requests. There are no deviations in style (e.g., no camelCase mixed in), making the naming predictable and readable. This consistency aids in understanding and using the tool set effectively.

    Tool Count3/5

    With 47 tools, the count is borderline high for a GitHub server, feeling heavy and potentially overwhelming. While GitHub is a broad domain, this many tools might indicate over-specialization or fragmentation. A more streamlined set could improve usability without sacrificing functionality, as some tools could be consolidated.

    Completeness5/5

    The tool set provides comprehensive coverage of GitHub's core functionalities, including repositories, issues, pull requests, projects, files, and search. It supports full CRUD/lifecycle operations (e.g., create, get, update, delete for issues and projects) and handles advanced workflows like project management and pull request reviews. No obvious gaps are present for the intended domain.

    Maintenance

    ActivityInactive
    ResponsivenessSyncing

    Resources