Skip to main content
Glama
DJeswar

io.github.DJeswar/github-issues

by DJeswar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to io.github.DJeswar/github-issues

No user-submitted related servers found.

    Related Servers

    • GitHub Issues MCP Server

      C-you-know
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to discover, filter, and triage GitHub issues across repositories, with tools for fetching issue details, listing issues by state/labels, and finding related pull requests.
      1
      MIT

    • github-issues-mcp

      nukathotipoojitha
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to list, search, and inspect issues on any public GitHub repository via natural language.
      MIT

    • github-mcp-server

      Rhytham4306
      F
      license
      Not graded
      quality
      C
      maintenance
      Connects an LLM to a GitHub repository's issues, allowing it to list, fetch, and search issues freely while gating new issues, comments, and closures behind a two-step, single-use confirmation token that cannot be bypassed. It provides least-privilege, token-authenticated access to the GitHub REST API through a small typed tool surface.
      -

    • github-updates

      Soller211
      A
      license
      A
      quality
      B
      maintenance
      Enables AI clients to search and read GitHub issues and pull requests, including full issue bodies and comments, through MCP tools. It returns compact JSON so agents can gather repository activity and draft project updates.
      2
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    A4.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: structural listing, single-issue retrieval, free-text search, label metadata, and milestone metadata. List_issues and search_issues are the only potentially overlapping pair, but their descriptions explicitly separate structural filtering from text search.

    Naming Consistency5/5

    Every tool follows a consistent lower_snake_case verb_noun pattern: list_*, get_*, and search_*. There are no mixed conventions, vague verbs, or inconsistent phrasing.

    Tool Count5/5

    Five tools is a well-scoped count for a read-only GitHub issue exploration server. Each tool earns its place and the set feels compact rather than redundant.

    Completeness5/5

    For the clearly read-only domain, coverage is complete: list/get/search handle issue discovery and retrieval, get_issue optionally includes comments, and labels/milestones cover the metadata needed for filtering and release planning. Mutation tools are intentionally absent rather than missing.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources