Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GitHub: Register Pull Request Operation Tools #560

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

vudayani
Copy link

Description

This PR adds the registration of tools to enhance pull request operations in the GitHub MCP server.

The following tools are registered:

list_pull_requests: List and filter pull requests in a GitHub repository
get_pull_request: Retrieve details of a specific pull request in a GitHub repository
get_pull_request_status: Get the combined status of all checks for a pull request
get_pull_request_files: Fetch the list of files changed in a pull request

Server Details

  • Server: github
  • Changes to: tools

Motivation and Context

  • Greatly enhances the usability of the server by providing critical pull request-related operations
  • Helps automate workflows and provides better support for managing GitHub pull requests

How Has This Been Tested?

The tools have been tested against GitHub repositories in the following scenarios:

  • Listing pull requests with various filters applied
  • Fetching details of individual pull requests
  • Retrieving status checks for pull requests
  • Fetching files changed in pull requests

Breaking Changes

  • No breaking changes as this is a non-disruptive addition of new tools
  • No changes are required to existing MCP configurations

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Protocol Documentation
  • My changes follows MCP security best practices
  • I have updated the server's README accordingly
  • I have tested this with an LLM client
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have documented all environment variables and configuration options

Additional context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant