Retrieve comprehensive pull request details including title, state, description, reviewers, and draft status to facilitate informed review and merge decisions.
MIT
700,429 tools. Updated 2026-10-25 02:34
"Assistance with reviewing and merging code changes in a merge request" matching MCP tools:
- Open a pull request from the agent work-cycle branch to propose code changes for review, without merging them directly.MIT
- List files changed in a GitLab merge request with stats and reviewability flags. Sort reviewable files first to prioritize high-value code review.MIT
- Update an existing trigger in Google Tag Manager by merging changes into its current configuration. Concurrent edits are prevented with a fingerprint check.Apache 2.0
- Retrieve the raw diff of a pull request to review code changes. Requires the pull request ID.MIT
- Merge an open GitLab merge request, with an optional source-branch SHA pin so the merge is rejected if newer commits moved the branch.MIT
Matching MCP Servers
- AlicenseBqualityDmaintenanceA Model Context Protocol server that helps large language models process code repositories by providing file tree generation, code merging, and code analysis capabilities.321MIT
Merge MCP Serverofficial
FlicenseNot gradedqualityDmaintenanceProvides integration between Merge API and LLM providers supporting the MCP protocol, allowing natural language interaction with Merge data across HRIS, ATS, and other categories.20-
Matching MCP Connectors
Point-in-time amendment history for 528 UK law provisions: search, version history, changes.
Live, sourced changes feed: Apple, Google Play, Android, GitHub, Vercel, Cloudflare, Firebase, more.
- End a sandbox session: submit preserves the fork for human review and merge, while discard deletes the fork and all changes. Merging is a human decision.MITDestructive
- Merge a pull request by number using merge, squash, or rebase strategies, with optional custom commit title/message and SHA guard to confirm branch state.MIT
- Retrieve detailed merge request information including status, pipelines, approvals, and conflicts to review and assess merge readiness in GitLab projects.Apache 2.0
- Close a GitLab merge request without merging to abandon changes or defer work. The request can be reopened later if needed.Apache 2.0
- Approve merge requests after code review completion to enable merging. Use when changes are approved and ready for integration.Apache 2.0
- Compare two Git references to review changes between branches, tags, or commits before merging. Shows commits and diffs to understand what changed between two points in a GitLab project.Apache 2.0
- Retrieve detailed file changes and complete diffs for a GitLab merge request to review code modifications with full context.Apache 2.0
- Create a pull request to merge changes from one branch to another. Automatically detects the source branch and selects the destination, with optional reviewer assignment.MIT
- List paginated merge request discussion threads with author, message preview, and resolved status for general and code-line comments. Use for an overview before fetching full details.Apache 2.0
- Start a discussion on a merge request in GitFlic. Add a general comment or specify line and path details to comment on specific code changes.Apache 2.0
- Merge duplicate nodes into one canonical node, redirecting all edges and aliases. Use after reviewing dedup candidates to resolve ambiguous duplicates.Apache 2.0
- Merge a change request using ff-only, no-fast-forward, squash, or rebase merge types, with optional merge message and source-branch deletion. Rewrites the target branch irreversibly.Apache 2.0
- Audits git diffs and pull requests for AI-hallucinated packages, typosquatting, unauthorized boundary imports, and leaked secrets to verify code changes before merging.Apache 2.0
- Generate concise AI-friendly summaries of GitLab merge requests to review key changes, discussions, and status within limited context windows for quick understanding and decision making.Apache 2.0
- Generate a unified chronological timeline merging oncology documents and conversation entries for reviewing medical history, sharing with doctors, or writing patient journals.MIT