GitHub PR Comments MCP Server
Fetches GitHub Pull Request comments with file paths, line ranges, and replies using GitHub API, providing a structured JSON format of the comments for analysis
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@GitHub PR Comments MCP Serverget comments for PR #42 in octocat/Hello-World"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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 claudeInstalling Manually
Clone the repository
Install dependencies:
npm installCreate a
.envfile with your GitHub token:GITHUB_TOKEN=your_github_token_here
Usage
Build the project:
npm run buildRun the server:
npm startOr directly with a GitHub token:
node dist/server.js your_github_token_hereThe server exposes a tool called
get_pr_commentsthat accepts the following parameters:owner: Repository owner (username or organization)repo: Repository namepull_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_hereReplace /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:
Build the project:
npm run buildRun 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 devLicense
ISC
Available Tools
1 toolget_pr_commentsD
| Name | Required | Description | Default |
|---|---|---|---|
| owner | Yes | Repository owner (username or organization) | |
| repo | Yes | Repository name | |
| pull_number | Yes | Pull request number |
TDQS
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.
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.
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.
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.
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.
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 tool update
- First observed
get_pr_comments
TDQS
With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is inherently distinct by default.
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.
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.
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
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
Create, deploy, and operate MCP servers directly from your GitHub repositories.
A MCP server built for developers enabling Git based project management with project and personal…
An MCP server that gives your AI access to the source code and docs of all public github repos
Related MCP Servers
- AlicenseAqualityBmaintenanceA secure MCP server for interacting with GitHub issues, pull requests, repository files, and search, supporting both github.com and GitHub Enterprise Server.11AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceAn MCP server that enables checking GitHub and Codeberg PR reviews, change requests, and conversations.MIT
- AlicenseBqualityCmaintenanceAn MCP server that collects Pull Request comments from private GitHub repositories, including issue comments, review comments, and review summaries.119MIT
- AlicenseAqualityCmaintenanceA production-ready MCP server for triaging and reviewing GitHub pull requests via the GitHub REST API, providing typed tools to list, inspect, comment, add labels, and submit reviews.810MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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