Skip to main content
Glama
shaileshahuja

GitHub PR Comments MCP Server

Servidor MCP de comentarios de PR de GitHub

insignia de herrería

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 claude

Instalación manual

  1. Clonar el repositorio

  2. Instalar dependencias:

    npm install
  3. Crea un archivo .env con tu token de GitHub:

    GITHUB_TOKEN=your_github_token_here

Uso

  1. Construir el proyecto:

    npm run build
  2. Ejecutar el servidor:

    npm start

    O directamente con un token de GitHub:

    node dist/server.js your_github_token_here
  3. El servidor expone una herramienta llamada get_pr_comments que acepta los siguientes parámetros:

    • owner : Propietario del repositorio (nombre de usuario u organización)

    • repo : Nombre del repositorio

    • pull_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_here

Reemplaza /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:

  1. Construir el proyecto:

    npm run build
  2. Ejecute 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 dev

Licencia

ISC

Available Tools

1 tool
get_pr_commentsD
ParametersJSON Schema
NameRequiredDescriptionDefault
ownerYesRepository owner (username or organization)
repoYesRepository name
pull_numberYesPull request number

TDQS

D1/5.0
Behavior1/5

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.

Conciseness1/5

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.

Completeness1/5

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.

Parameters1/5

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.

Purpose1/5

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.

Usage Guidelines1/5

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. 1 tool update
    • First observedget_pr_comments

TDQS

D1.7/5.0

Scored 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.

Maintenance

ActivityInactive
ResponsivenessNo issues

Related MCP Connectors

Related MCP Servers