Skip to main content
Glama
Sign In
github-tools

github-tools

by craft-agent
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to github-tools

No user-submitted related servers found.

    Related Servers

    • GitHub MCP Server

      Yash-R09
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to interact with GitHub through the GitHub REST API, supporting repository, file, issue, pull request, branch, commit, search, and label operations with explicit confirmation for write operations.
      -

    • GitHub MCP Server

      pipseedai
      A
      license
      A
      quality
      Not graded
      maintenance
      Enables AI agents to interact with GitHub repositories through the GitHub REST API for managing files, issues, and repository metadata. It supports both read operations like searching code and write operations such as creating repositories and updating issue comments.
      9
      -

    • GitHub MCP Server (Custom)

      rishav0004
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to perform full CRUD operations on GitHub, including repositories, issues, pull requests, branches, comments, reviews, and merges through the Model Context Protocol.
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.2/5.0

    Scored across 8 tools

    Disambiguation4/5

    Each tool has a distinct primary purpose (create, read, edit, comment, close, reopen, relate, develop), and the descriptions clearly delineate state transitions (close/reopen) from field edits (edit) and from relation management (relate). Minor overlap exists since close/reopen can post a comment and create/edit/relate all touch labels, assignees, and parent issues, but the boundaries are explained well enough that misselection is unlikely.

    Naming Consistency5/5

    All eight tools follow the identical github_issue_<verb> pattern with short, predictable verbs (close, reopen, relate, develop, read, create, edit, comment). There are no style deviations or mixed conventions.

    Tool Count5/5

    Eight tools is well within the ideal 3-15 range and each tool maps to a real issue-lifecycle operation, so nothing feels redundant or padded. The surface is tightly scoped to issue management.

    Completeness4/5

    The core issue lifecycle is fully covered: create, read (view/list), edit, comment, close, reopen, plus relation and linked-branch management. Minor gaps remain, such as no dedicated comment listing/editing, no label or milestone management tools (only create_milestone flags), and no lock/transfer/pin operations.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources