Skip to main content
Glama
jamesjfoong

github-pr-review-mcp

by jamesjfoong
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to github-pr-review-mcp

No user-submitted related servers found.

    Related Servers

    • git-reviewer

      Suchit-007
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to fetch GitHub pull request diffs and metadata, and post review comments directly through the MCP protocol.
      1
      MIT

    • pr-forge

      wang654993222
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides AI agents with a secure PR review gateway through 9 MCP tools for managing pull requests, including context retrieval, diff, checks, and merge with two-layer access control.
      14
      MIT

    • GitLab Review MCP

      lininn
      A
      license
      B
      quality
      C
      maintenance
      Enables code review operations on GitHub and GitLab, including fetching pull/merge requests, viewing diffs, adding comments, analyzing code quality, and creating merge requests directly from your MCP client.
      15
      11
      4
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 14 tools

    Disambiguation4/5

    Each tool has a clear primary target—PR metadata, files, diff hunks, comments, reviews, pending review state, or submission—and the specialized helpers like validate_pr_comment_target and ensure_pending_review are distinct. Minor ambiguity remains between get_pr_files and get_pr_diff_hunks, and between get_pr_comments and get_pr_reviews/list_pending_review_comments, but descriptions generally disambiguate granularity.

    Naming Consistency5/5

    Tool names follow a consistent verb_noun pattern throughout: get_, add_, submit_, update_, ensure_, list_, analyze_, validate_, and review_. The naming style is uniform and the PR object is always clearly identified, making selection predictable.

    Tool Count5/5

    14 tools is well within the ideal scope for a PR review server. Each tool covers a distinct step of the workflow—from reading PR data and diff hunks to managing pending reviews and submitting—without meaningful redundancy.

    Completeness4/5

    The tool surface covers the core PR review lifecycle: fetching PR details, files, diff hunks, reviews/comments, analyzing code, creating/managing pending reviews, adding comments, validating targets, and submitting reviews. Notable minor gaps are the absence of explicit editing/deleting for pending review comments and no dismissal or revision-handling tools, but these do not dead-end the primary workflow.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources