Skip to main content
Glama
enesjakozh
shaileshahuja

GitHub PR Comments MCP Server

by shaileshahuja
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GitHub PR 评论 MCP 服务器

铁匠徽章

这是一个模型上下文协议 (MCP) 服务器，它使用 GitHub 个人访问令牌获取 GitHub Pull Request 评论。

特征

  • 获取带有文件路径、行范围和回复的 PR 评论

  • 通过 Octokit 使用 GitHub API

  • 使用 StdioServerTransport 实现 MCP 服务器

  • 以结构化的 JSON 格式返回评论

Related MCP server: PR Reviews MCP Server

安装

通过 Smithery 安装

通过Smithery自动为 Claude Desktop 安装 github-pr-mcp：

npx -y @smithery/cli install github-pr-mcp --client claude

手动安装

  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 集成，请在 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