MCP for GitHub PR, Issues, Tags and Releases

Created By
saidsefa year ago
A Model Context Protocol (MCP) application for automated GitHub PR analysis and issue management. Enables LLMs to fetch PR details, analyse diffs, manage issues, and handle releases through a standardised interface
Overview

What is MCP for GitHub PR, Issues, Tags and Releases?

MCP for GitHub is a Model Context Protocol (MCP) application designed for automated analysis of GitHub pull requests (PRs) and issue management, enabling seamless integration with Large Language Models (LLMs).

How to use MCP for GitHub?

To use this tool, clone the repository from GitHub, install the required dependencies, and configure your desktop LLM to connect with the MCP server. You can then fetch PR details, create and update issues, and manage releases directly from your LLM.

Key features of MCP for GitHub?

  • Automated PR content retrieval and diff analysis.
  • Issue creation and updates with conventional commit prefixes.
  • Tag and release management with automatic release notes.
  • Network information retrieval for IPv4 and IPv6.

Use cases of MCP for GitHub?

  1. Streamlining PR analysis and updates in development workflows.
  2. Automating issue tracking and management for software projects.
  3. Facilitating release management and versioning in GitHub repositories.

FAQ from MCP for GitHub?

  • What is the requirement to run MCP for GitHub?

You need Python 3.11+ and a GitHub Personal Access Token with repo scope.

  • Can I integrate MCP with any LLM?

Yes, MCP can be integrated with any LLM that supports external tool connections.

  • Is there a contribution guide available?

Yes, you can find the contribution guide in the repository for more information on how to contribute.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
saidsef
Star
3
Language
Python
License
Apache-2.0 license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago