GitHub PR Comments MCP Server
Servidor MCP de comentarios de PR de GitHub
Este es un servidor de Protocolo de contexto de modelo (MCP) que obtiene los comentarios de las solicitudes de extracción de GitHub mediante un token de acceso personal de GitHub.
Características
Obtiene comentarios de PR con rutas de archivos, rangos de líneas y respuestas
Utiliza la API de GitHub a través de Octokit
Implementa el servidor MCP con StdioServerTransport
Devuelve comentarios en un formato JSON estructurado
Related MCP server: PR Reviews MCP Server
Instalación
Instalación mediante herrería
Para instalar github-pr-mcp para Claude Desktop automáticamente a través de Smithery :
npx -y @smithery/cli install github-pr-mcp --client claudeInstalación manual
Clonar el repositorio
Instalar dependencias:
npm installCrea un archivo
.envcon tu token de GitHub:GITHUB_TOKEN=your_github_token_here
Uso
Construir el proyecto:
npm run buildEjecutar el servidor:
npm startO directamente con un token de GitHub:
node dist/server.js your_github_token_hereEl servidor expone una herramienta llamada
get_pr_commentsque acepta los siguientes parámetros:owner: Propietario del repositorio (nombre de usuario u organización)repo: Nombre del repositoriopull_number: Número de solicitud de extracción
Integración con Cursor
Para integrarse con Cursor, utilice el siguiente comando en la configuración del servidor MCP de Cursor:
node /path/to/dist/server.js your_github_token_hereReemplaza /path/to con la ruta real a tu proyecto y your_github_token_here con tu token de acceso personal de GitHub.
Pruebas
Se incluye un cliente de prueba para verificar la funcionalidad del servidor:
Construir el proyecto:
npm run buildEjecute el cliente de prueba:
npm test
El cliente de prueba iniciará el servidor, se conectará a él y llamará a la herramienta get_pr_comments con parámetros de muestra.
Formato de respuesta
El servidor devuelve comentarios en el siguiente formato:
{
"comments": [
{
"id": 123456789,
"path": "src/example.js",
"body": "This is a comment on a specific line",
"line": 42,
"start_line": 40,
"user": {
"login": "username"
},
"created_at": "2023-01-01T00:00:00Z",
"replies": [
{
"id": 987654321,
"body": "This is a reply to the comment",
"user": {
"login": "another-username"
},
"created_at": "2023-01-02T00:00:00Z"
}
]
}
]
}Desarrollo
Para ejecutar el servidor en modo de desarrollo:
npm run devLicencia
ISC
Available Tools
1 toolget_pr_commentsD
| Name | Required | Description | Default |
|---|---|---|---|
| owner | Yes | Repository owner (username or organization) | |
| repo | Yes | Repository name | |
| pull_number | Yes | Pull request number |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- First observed
get_pr_comments
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is inherently distinct by default.
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.
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.
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.
Maintenance
Related MCP Connectors
Create, deploy, and operate MCP servers directly from your GitHub repositories.
A MCP server built for developers enabling Git based project management with project and personal…
An MCP server that gives your AI access to the source code and docs of all public github repos
Related MCP Servers
- AlicenseBqualityAmaintenanceA secure MCP server for interacting with GitHub issues, pull requests, repository files, and search, supporting both github.com and GitHub Enterprise Server.18AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables checking GitHub and Codeberg PR reviews, change requests, and conversations.MIT
- AlicenseBqualityCmaintenanceAn MCP server that collects Pull Request comments from private GitHub repositories, including issue comments, review comments, and review summaries.118 npmMIT
- AlicenseAqualityCmaintenanceA 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.89 npmMIT