MCP for GitHub PR, Issues, Tags and Releases
The Model Context Protocol (MCP) is an open standard that enables seamless integration between Large Language Models (LLMs) and external tools. Whilst it can be implemented in any AI system, including custom LLM setups, the degree of integration and optimisation varies based on the model's architecture and capabilities.
This MCP application serves as a bridge between LLMs and GitHub's repository management features, offering automated analysis of pull requests and comprehensive issue management. It provides a robust set of tools to fetch PR details, create issues, and update issues directly from your desktop LLM. The application is designed with modularity in mind, supporting extensibility via the MCP tool interface and seamless integration with existing workflows.
The toolset enables automated PR analysis, issue tracking, tagging and release management through a standardised MCP interface, making it ideal for teams seeking to streamline their GitHub workflow automation.
Features
| Function | Description |
|---|---|
| Analyse GitHub Pull Requests and fetch diffs | Retrieve the diff/patch for any PR in a repository. |
| Fetch content and metadata for specific PRs | Get PR title, description, author, timestamps, and state. |
| Update PR title and description | Change the title and body of any PR. |
| Add comments to PRs | Post general comments to a PR thread. |
| Add inline review comments to PRs | Comment on specific lines in PR files for code review. |
| Create and update GitHub Issues | Open new issues or update existing ones with title, body, labels, and state. |
| Create tags and releases | Tag repository commits and publish releases with changelogs. |
| Retrieve IPv4 and IPv6 information | Get public IP address details for both IPv4 and IPv6. |
| List all open Issues or Pull Requests | View all open PRs or issues for any user or organisation. |
Requirements
- Python 3.11+
- GitHub Personal Access Token (with
reposcope)
Architecture Diagram
+------------------------+
| |
| MCP Client/User |
| |
+------------------------+
|
| (stdio/http)
v
+--------------------+ +------------------------+
| | | PRIssueAnalyser |
| IP Integration | <------------| (FastMCP Server) |
| (ipinfo.io) | | |
+--------------------+ +------------------------+
|
| (API calls)
v
+------------------------+
| GitHub Integration |
+------------------------+
|
| (REST API)
+-------------------------+-------------------------+
| | |
+-------------+ +--------------+ +-------------+
| GitHub PRs | |GitHub Issues | |GitHub Tags/ |
| & Releases | | | | Releases |
+-------------+ +--------------+ +-------------+
Features:
- PR Management: Fetch, analyze, and update
- Issue Tracking: Create and update
- Release Management: Tags and releases
- Network Info: IPv4/IPv6 details
Main Flows:
- PRIssueAnalyser: Main MCP server handling tool registration and requests
- GitHub Integration: Manages all GitHub API interactions
- IP Integration: Handles IPv4/IPv6 information retrieval
- MCP Client: Interacts via stdio or streamable HTTP (http)
Local Installation
- Clone the repository:
git clone https://github.com/saidsef/mcp-github-pr-issue-analyser.git
cd mcp-github-pr-issue-analyser
- Install dependencies:
Launch MCP in stdio mode.
export GITHUB_TOKEN="<github-token>"
uvx ./
Alternatively, launch MCP in http mode.
export GITHUB_TOKEN="<github-token>"
export MCP_ENABLE_REMOTE=true
uvx ./
You can access it via
httpi.e.http(s)://localhost:8080/mcp
Local Integration with IDEs and LLMs
To add an MCP server to your IDE or LLM, you need to add this section to the configuration file. The basic structure involves defining a server name and providing the command and any necessary arguments to run the server.
Claude / Cursor / Windsurf
{
"mcpServers": {
"github_prs_issues": {
"command": "uvx",
"env": {
"GITHUB_TOKEN": "<your-github-token>"
},
"args": [
"https://github.com/saidsef/mcp-github-pr-issue-analyser.git",
]
}
}
}
VS Code
{
"inputs": [
{
"type": "promptString",
"id": "github-token",
"description": "Enter your GitHub token",
"password": true
}
],
"servers": {
"github-prs-issues": {
"type": "stdio",
"command": "uvx",
"args": [
"https://github.com/saidsef/mcp-github-pr-issue-analyser.git",
],
"env": {
"GITHUB_TOKEN": "${input:github-token}"
}
}
}
}
Source
Our latest and greatest source of mcp-github-pr-issue-analyser can be found on [GitHub]. Fork us!
Contributing
We would ❤️ you to contribute by making a pull request.
Please read the official Contribution Guide for more information on how you can contribute.
Metadata
Release files for iflow-mcp_mcp-github-pr-issue-analyser 3.4.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| iflow_mcp_mcp_github_pr_issue_analyser-3.4.2.tar.gz | 15.7 kB | Without provenance | Details for iflow_mcp_mcp_github_pr_issue_analyser-3.4.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| iflow_mcp_mcp_github_pr_issue_analyser-3.4.2-py3-none-any.whl | Python 3 | none | any | Details for iflow_mcp_mcp_github_pr_issue_analyser-3.4.2-py3-none-any.whl |
Total release size: 33.4 kB
Release files / iflow_mcp_mcp_github_pr_issue_analyser-3.4.2.tar.gz
| Download URL | iflow_mcp_mcp_github_pr_issue_analyser-3.4.2.tar.gz |
|---|---|
| Size | 15.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2a05e1b82e2017ea03ea62c811b0c48df3c1299f9faa562141b65fbedd01ad83
|
|
BLAKE2b-256 checksum How to use checksums |
6b6b8dc45ac7f1c3c8d0da1d77c00e0855776a48ad1cc9f01ede81d533e42b04
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.6.17
|
Release files / iflow_mcp_mcp_github_pr_issue_analyser-3.4.2-py3-none-any.whl
| Download URL | iflow_mcp_mcp_github_pr_issue_analyser-3.4.2-py3-none-any.whl |
|---|---|
| Size | 17.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
518cdafdf60e20793e0a83eac0efc6fd60d22256a7758b4f8041fd8973b62129
|
|
BLAKE2b-256 checksum How to use checksums |
891beef03d1b43d7377852edb74747226109360d1deadef96a98ac0799d78d91
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.6.17
|
Security for iflow-mcp_mcp-github-pr-issue-analyser 3.4.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.