Github PR Comments MCP Server

Fetches comments from GitHub Pull Requests, including file paths, line ranges, and replies, using a personal access token.

Local serverstdio 3

What is the Github PR Comments MCP server?

Github PR Comments MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Fetches comments from GitHub Pull Requests, including file paths, line ranges, and replies, using a personal access token.

What you get

This is a Model Context Protocol (MCP) server that fetches GitHub Pull Request comments using a GitHub personal access token.

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

Setting it up

Installation goes through your MCP client rather than a global install: point it at @smithery/cli on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

What the assistant can call

Once Github PR Comments is connected, these are the calls the assistant has available:

  • owner — Repository owner (username or organization)
  • repo — Repository name
  • pull_number — Pull request number

Configuration and credentials

You will need one environment variable: GITHUB_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the github pr comments mcp server does with a few real requests.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Github PR Comments's toolset — owner, repo, pull_number — is a fair guide to whether it matches your workflow. It is maintained by shaileshahuja; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Github PR Comments's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
ownerRepository owner (username or organization)
repoRepository name
pull_numberPull request number

How to install the Github PR Comments MCP server

{
  "mcpServers": {
    "github-pr-comments": {
      "command": "npx",
      "args": ["-y", "@smithery/cli"],
      "env": {
        "GITHUB_TOKEN": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
GITHUB_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use Github PR Comments to owner.
  • Use Github PR Comments to repo.
  • Use Github PR Comments to pull number.

Frequently asked questions

You can install it manually by cloning the repository and using npm, or automatically via Smithery. You'll need a GitHub personal access token. See the installation and usage sections in the documentation for detailed steps.