Skip to main content
Glama
yangchoi

github-triage-mcp

by yangchoi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to github-triage-mcp

No user-submitted related servers found.

    Related Servers

    • Prodbeam MCP Server

      prodbeam
      A
      license
      A
      quality
      C
      maintenance
      Generates engineering intelligence reports (standups, weekly summaries, sprint retrospectives) from GitHub and Jira data, accessible via MCP clients or CLI.
      10
      1 npm
      MIT

    • standup-mr

      Jubstaaa
      A
      license
      A
      quality
      A
      maintenance
      Generates a daily standup note from GitLab merge request or GitHub pull request state: what is ready to merge, what is blocked, what is stale, and what is waiting on your review. When CI is red it opens the failed job's log and reports the error lines, so the note says why the pipeline failed rather than just that it did.
      2
      3
      173 npm
      MIT

    • SwarmBridge

      Wersky
      A
      license
      Not graded
      quality
      C
      maintenance
      Turns a shared GitHub repository into a message bus so that agents and their subagents on two different machines can converse in parallel: an issue is a thread, a comment is a reply, and closing it is an acknowledgement. Provides zero-dependency tools for sending addressed or broadcast messages, incrementally polling an inbox with a per-identity cursor, reading and replying within threads, and closing the loop with an ack.
      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

    A3.9/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool serves a distinct purpose: triage provides an overview, get_issue retrieves full thread content, search_issues queries by syntax, and linked_issues discovers cross-references. There is no overlap or ambiguity between them.

    Naming Consistency3/5

    get_issue and search_issues follow a clear verb_noun pattern, but triage is a bare imperative and linked_issues is a descriptive noun phrase rather than an action. The mixed conventions are still readable, but not fully consistent.

    Tool Count5/5

    Four tools is exactly right for a focused triage server. Each tool covers a necessary step in the triage workflow without redundancy or bloat.

    Completeness5/5

    The tool surface covers the complete read-only triage workflow: get an overview, drill into full details, search, and trace relationships between issues and PRs. No obvious gaps exist for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources