MCP.so
ログイン

GitHub PR Comments MCP Server

@shaileshahuja

基本情報

カテゴリ

バージョン管理

ライセンス

MIT

トランスポート

stdio

作者

shaileshahuja

GitHub PR Comments MCP Server について

MCP server that fetches GitHub Pull Request comments

GitHub PR Comments MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "github-pr-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@smithery/cli",
        "install",
        "github-pr-mcp",
        "--client",
        "claude"
      ]
    }
  }
}

GitHub PR Comments MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

上のボタンで一時的なサンドボックスでこのサーバーを実行し、ツール一覧を取得できます。

概要

What is GitHub PR Comments MCP Server?

A Model Context Protocol server that fetches GitHub Pull Request comments using a GitHub personal access token. It is for developers who want to programmatically retrieve PR comments with file paths, line ranges, and replies.

How to use GitHub PR Comments MCP Server?

Clone the repository, install dependencies with npm install, create a .env file with a GITHUB_TOKEN, build with npm run build, and run with npm start or directly with node dist/server.js your_github_token_here. The server exposes a tool called get_pr_comments that accepts owner, repo, and pull_number parameters.

Key features of GitHub PR Comments MCP Server

  • Fetches PR comments with file paths, line ranges, and replies
  • Uses GitHub API via Octokit
  • Implements MCP server with StdioServerTransport
  • Returns comments in structured JSON format

Use cases of GitHub PR Comments MCP Server

  • Automating code review summarization by extracting PR comments and replies
  • Integrating PR comment data into custom workflows or dashboards
  • Programmatically analyzing PR feedback across repositories

よくある質問

1

What does this server do compared to alternatives?

It provides a simple MCP interface to fetch PR comments using a GitHub personal access token, returning structured JSON with file paths, line ranges, and threaded replies.

2

What dependencies or runtime requirements are needed?

Node.js, npm, and a GitHub personal access token stored in a `.env` file as `GITHUB_TOKEN`.

3

Where does data live?

All data is fetched live from the GitHub API; no local storage of comments.

4

What transport does the server use?

It uses StdioServerTransport (stdio transport) for MCP communication.

5

How is authentication handled?

Authentication requires a GitHub personal access token, provided via environment variable or command-line argument.

コメント

「バージョン管理」の他のコンテンツ