Retrieve comprehensive pull request details including title, state, description, reviewers, and draft status to facilitate informed review and merge decisions.
MIT
220,252 tools. Last updated 2026-06-21 11:13
"Assistance with reviewing and merging code changes in a merge request" matching MCP tools:
- Creates a proposed change (pull request) from the active session branch to the default branch for human review, approval, and merge.Apache 2.0
- Create comments on change requests, either globally on the entire merge request or inline on specific code lines with file path and line number.Apache 2.0
- Update a local repository with upstream changes before starting work by fetching and integrating changes from a remote. Specify repo path, optionally branch, remote (default origin), and strategy (merge or rebase).MIT
- Create a change request (merge request) with source/target branches, reviewers, associated work items, and optional AI review trigger.Apache 2.0
- Retrieve all patch set versions for a change request. Provide organization, repository, and local ID to see the evolution of the merge request.Apache 2.0
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.Last updated322MIT
Merge MCP Serverofficial
Flicense-qualityDmaintenanceProvides integration between Merge API and LLM providers supporting the MCP protocol, allowing natural language interaction with Merge data across HRIS, ATS, and other categories.Last updated18
Matching MCP Connectors
Corporate travel: search and book flights, hotels, rail and transfers, manage orders.
Cloudflare Workers MCP server: api-request-deduplicator
- Retrieve detailed information about a specific change request (merge request) using its local ID within an Alibaba Cloud DevOps repository.Apache 2.0
- Compares two versions of code to identify improvements, regressions, and neutral changes. Returns a merge recommendation for code review and refactoring validation.MIT
- Retrieve detailed merge request information including status, pipelines, approvals, and conflicts to review and assess merge readiness in GitLab projects.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
- Close a GitLab merge request without merging to abandon changes or defer work. The request can be reopened later if needed.Apache 2.0
- Merge an approved GitLab merge request after meeting prerequisites like approvals and CI passing. Supports options for squash commits, branch deletion, and auto-merge on pipeline success.Apache 2.0
- Retrieve changed file paths in a GitLab merge request without diff content. Specify the merge request by IID or source branch.MIT
- Approve merge requests after code review completion to enable merging. Use when changes are approved and ready for integration.Apache 2.0
- Reviews code changes before merge by reading the diff, identifying risks, running tests, and providing a section-by-section verdict with confirmation gates. Ensures safe merging only after fresh verification.Apache 2.0
- Retrieve merge request diffs with pagination by providing project ID and either merge request IID or source branch.MIT
- Generate a unified chronological timeline merging oncology documents and conversation entries for reviewing medical history, sharing with doctors, or writing patient journals.MIT
- Close a pull request without merging it, keeping the branch intact.MIT
- 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