Skip to main content
Glama
shaileshahuja

GitHub PR Comments MCP Server

GitHub PR Comments MCP Server

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

Features

  • 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

Related MCP server: PR Reviews MCP Server

Installation

Installing via Smithery

To install github-pr-mcp for Claude Desktop automatically via Smithery:

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

Installing Manually

  1. Clone the repository

  2. Install dependencies:

    npm install
  3. Create a .env file with your GitHub token:

    GITHUB_TOKEN=your_github_token_here

Usage

  1. Build the project:

    npm run build
  2. Run the server:

    npm start

    Or directly with a GitHub token:

    node dist/server.js your_github_token_here
  3. The server exposes a tool called get_pr_comments that accepts the following parameters:

    • owner: Repository owner (username or organization)

    • repo: Repository name

    • pull_number: Pull request number

Integration with Cursor

To integrate with Cursor, use the following command in Cursor's MCP server configuration:

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

Replace /path/to with the actual path to your project, and your_github_token_here with your GitHub personal access token.

Testing

A test client is included to verify the server functionality:

  1. Build the project:

    npm run build
  2. Run the test client:

    npm test

The test client will start the server, connect to it, and call the get_pr_comments tool with sample parameters.

Response Format

The server returns comments in the following format:

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

Development

To run the server in development mode:

npm run dev

License

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. Dates show when Glama detected each change.

  1. 1 tool update
    • First observedget_pr_comments

TDQS

D1.7/5.0
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
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/shaileshahuja/github-pr-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server