Skip to main content
Use MCP tools to generate reports on review activity and track team progress.

​
PR Status

Get a quick status check for any PR: 
What's the review status for PR #5 in owner/repo?
Individual PR stats
Tool: get_merge_request Response includes:
  • reviewCompleteness: “2/5 Greptile comments addressed”
  • hasNewCommitsSinceReview: Whether re-review needed
  • addressedComments / unaddressedComments: Full lists

​
Weekly Summary

Generate a report of open PR status: 
Give me a weekly summary of all open PRs with their review status and make a nice visual graph for important stats.
PR report visualization
The assistant:
  1. Calls list_pull_requests with state: "open"
  2. For each PR, calls get_merge_request to get reviewAnalysis
  3. Compiles: PR number, title, author, age, completeness, unaddressed count
Claude took the MCP data and whipped up a basic webpage to visualize it.

​
Team Metrics

How many unaddressed Greptile comments do we have per repository?
Tool: list_pull_requests + list_merge_request_comments for each
What percentage of Greptile comments have been addressed across all open PRs?
Tool: get_merge_request → aggregates reviewAnalysis across PRs
Which open PRs are older than 7 days and still have unaddressed comments?
Tool: list_pull_requests → filters by createdAt
How many unaddressed comments have suggested code fixes?
Tool: search_greptile_comments → checks summary.withSuggestions
Which files have the most unaddressed Greptile comments?
Tool: search_greptile_comments → groups by filePath

​
Code Review History

Show me the last 10 completed code reviews
Tool: list_code_reviews with status: "COMPLETED" and limit: 10
Get details for code review 1382118
Tool: get_code_reviewReturns strictness, totalFiles, completedFiles, full PR info.
Are there any failed or skipped code reviews?
Tool: list_code_reviews with status: "FAILED" or "SKIPPED"

​
Next Steps

Auto-Fix Workflow

Fix issues identified in your reports

Custom Context

Track which patterns trigger the most comments