Skip to main content
Glama
enesjakozh
shaileshahuja

GitHub PR Comments MCP Server

by shaileshahuja
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GitHub PR 댓글 MCP 서버

대장간 배지

이는 GitHub 개인 액세스 토큰을 사용하여 GitHub 풀 리퀘스트 코멘트를 가져오는 MCP(모델 컨텍스트 프로토콜) 서버입니다.

특징

  • 파일 경로, 줄 범위 및 답변이 포함된 PR 주석을 가져옵니다.

  • Octokit을 통해 GitHub API를 사용합니다.

  • StdioServerTransport를 사용하여 MCP 서버를 구현합니다.

  • 구조화된 JSON 형식으로 주석을 반환합니다.

Related MCP server: PR Reviews MCP Server

설치

Smithery를 통해 설치

Smithery를 통해 Claude Desktop에 github-pr-mcp를 자동으로 설치하려면:

지엑스피1

수동 설치

  1. 저장소를 복제합니다

  2. 종속성 설치:

    npm install

  3. GitHub 토큰으로 .env 파일을 만듭니다.

    GITHUB_TOKEN=your_github_token_here

용법

  1. 프로젝트를 빌드하세요:

    npm run build

  2. 서버를 실행합니다:

    npm start

    또는 GitHub 토큰을 사용하여 직접:

    node dist/server.js your_github_token_here

  3. 서버는 다음 매개변수를 허용하는 get_pr_comments 라는 도구를 제공합니다.

    • owner : 저장소 소유자(사용자 이름 또는 조직)

    • repo : 저장소 이름

    • pull_number : 풀 리퀘스트 번호

커서와의 통합

Cursor와 통합하려면 Cursor의 MCP 서버 구성에서 다음 명령을 사용하세요.

node /path/to/dist/server.js your_github_token_here

/path/to 프로젝트의 실제 경로로 바꾸고, your_github_token_here GitHub 개인 액세스 토큰으로 바꾸세요.

테스트

서버 기능을 검증하기 위해 테스트 클라이언트가 포함되었습니다.

  1. 프로젝트를 빌드하세요:

    npm run build

  2. 테스트 클라이언트를 실행합니다.

    npm test

테스트 클라이언트는 서버를 시작하고 서버에 연결한 다음 샘플 매개변수를 사용하여 get_pr_comments 도구를 호출합니다.

응답 형식

서버는 다음 형식으로 주석을 반환합니다.

{
  "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"
        }
      ]
    }
  ]
}

개발

개발 모드에서 서버를 실행하려면:

npm run dev

특허

아이에스씨

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

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

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches