Repository navigation
Add pagination support for get_pull_request_diff to handle large PRs #625
Description
Problem
The get_pull_request_diff function currently fails when attempting to fetch diffs for large pull requests that exceed the token limit. This makes it impossible to analyze changes in PRs with substantial modifications.
Example Error
Error: MCP tool "get_pull_request_diff" response (36464 tokens) exceeds maximum allowed tokens (25000).
Please use pagination, filtering, or limit parameters to reduce the response size.
This error was encountered when trying to fetch the diff for velero-io/velero#9019
Proposed Solution
Add pagination support to the get_pull_request_diff function to handle large diffs by:
- Implementing pagination parameters (e.g.,
page,per_page, or file-based pagination) - Adding options to filter by specific files or paths
- Supporting partial diff retrieval with offset/limit parameters
Use Case
This enhancement would enable users to:
- Analyze large pull requests without hitting token limits
- Retrieve diffs incrementally for better performance
- Focus on specific files or directories within a PR
Alternative Workarounds
Currently, users must resort to other methods like:
- Using
get_pull_request_filesto list changed files - Fetching individual file contents
- Using the GitHub CLI or API directly
Having built-in pagination would provide a more seamless experience for MCP users working with large codebases.
Activity
MrKoopie commentedon Jul 27, 2025
I have a similar situation. Sometimes PRs have a lot of feedback. Especially with tools such as CodeRabbit. Having proper navigation, but also the option to filter out resolved items, would help.
tanapat-ratana-r10 commentedon Aug 19, 2025
I really need this feature right now.
tabletenniser commentedon Aug 21, 2025
Same, need this to handle large PRs!
github-actions commentedon Feb 17, 2026
This issue is stale because it has been open for 30 days with no activity. Leave a comment to avoid closing this issue in 60 days.
github-actions commentedon May 13, 2026
This issue is stale because it has been open for 30 days with no activity. Leave a comment to avoid closing this issue in 60 days.
github-actions commentedon Aug 19, 2026
This issue was closed because it has been inactive for 60 days since being marked as stale.