GitHub PR Comments MCP Server

Related Servers

Alternatives to GitHub PR Comments MCP Server

No user-submitted related servers found.

Related Servers

GitHub PR Review MCP
Version Control Project Management Code Analysis
aq35
A
license
B
quality
C
maintenance
An MCP server that collects Pull Request comments from private GitHub repositories, including issue comments, review comments, and review summaries.
Updated 3 months ago (2026-07-08 21:57 UTC)
1
18 npm
MIT
GitHub PR MCP Server
Version Control Developer Tools
Pelado-Nerdworks
A
license
A
quality
C
maintenance
MCP server for interacting with GitHub Pull Requests, enabling listing, viewing, commenting, reviewing, and merging PRs.
Updated 2 months ago (2026-08-01 20:55 UTC)
6
64 npm
2
MIT
github-pr-review-mcp
Version Control Code Analysis
iabu94
F
license
Not graded
quality
C
maintenance
A local MCP server that reads GitHub pull request diffs and coding standards, then posts inline review comments and full reviews to PRs via any MCP client.
Updated 2 months ago (2026-07-30 18:48 UTC)
-
MCP GitHub CrunchTools
Version Control Developer Tools
crunchtools
A
license
A
quality
A
maintenance
A secure MCP server for interacting with GitHub issues, pull requests, repository files, and search, supporting both github.com and GitHub Enterprise Server.
Updated 2 days ago (2026-09-26 09:33 UTC)
18
AGPL 3.0
github-pr-control-mcp
Version Control Project Management Developer Tools
nexicturbo
A
license
A
quality
C
maintenance
A production-ready MCP server for triaging and reviewing GitHub pull requests via the GitHub REST API, providing typed tools to list, inspect, comment, add labels, and submit reviews.
Updated 2 months ago (2026-07-30 04:44 UTC)
8
5 npm
MIT
PR Reviews MCP Server
Version Control Developer Tools
thesuperRL
A
license
Not graded
quality
D
maintenance
An MCP server that enables checking GitHub and Codeberg PR reviews, change requests, and conversations.
Updated 3 months ago (2026-06-25 01:00 UTC)
MIT

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

D1.7/5.0

Scored 2026-04-18 11:10 across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is inherently distinct by default.

Naming Consistency5/5

A single tool inherently has consistent naming with itself. The name 'get_pr_comments' follows a clear verb_noun pattern, which would be consistent if more tools existed.

Tool Count2/5

One tool is too few for a server focused on GitHub PR comments, as it lacks basic CRUD operations like creating, updating, or deleting comments. This severely limits functionality for the apparent domain.

Completeness1/5

The tool set is severely incomplete for handling PR comments. It only provides a 'get' operation, missing essential actions like create, update, delete, or list, which are necessary for a functional comments interface.