Patch Node.js vulnerabilities in a GitHub-connected website by updating affected package versions and opening a pull request for review and merge.
MIT
471,114 tools. Updated 2026-08-23 20:08
"Assistance with reviewing and merging code changes in a merge request" matching MCP tools:
- Retrieve comprehensive pull request details including title, state, description, reviewers, and draft status to facilitate informed review and merge decisions.MIT
- Merge a code change request into the target branch using a specified merge type, with optional message and source branch deletion. Resolves the need to integrate code changes while controlling merge strategy.Apache 2.0
- Submit a code review decision (PASS/NOT_PASS) with an optional comment and pending draft comments in one operation, keeping merge request reviews on track.Apache 2.0
- Add a global or inline comment to a change request (merge request) in Alibaba Cloud DevOps, specifying content, line number, and patchset versions.Apache 2.0
- Create a change request (merge request) for your repository with specified source and target branches, reviewers, linked work items, and optional AI review trigger.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.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.18
Matching MCP Connectors
ifsc-in MCP — Indian bank branch IFSC code lookup via Razorpay's open
Self-authenticating booking-request receipt anchored to the Knox chain; never represents a person.
- List all patch sets (versions) of a merge request within a repository to track its evolution and review changes over time.Apache 2.0
- Fetches detailed information about a specific change request (merge request) by its local ID in a repository.Apache 2.0
- Merge a GitLab merge request after verifying approval, conflicts, and pipeline status. Optionally squash commits, auto-merge on pipeline success, or remove source branch. Requires merge permission and returns merge result or error.MIT
- Merges a branch session's changes into a target session using an automatic merge base from the fork point. Returns conflicts for manual resolution, then re-merges with resolutions to complete the merge.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
- Remove your approval from a merge request for the specified project, updating the review state. Use when you need to revoke a previously submitted approval before merging.MIT
- Resolve or unresolve a merge request review thread by discussion ID. Mark threads as resolved to complete review discussions, with permission checks and updated discussion returned.MIT
- Retrieve the raw diff of a pull request to review code changes. Requires the pull request ID.MIT
- Update a Google Tag Manager variable by merging changes into its current configuration, preserving concurrent edits with fingerprint checks.Apache 2.0
- Detect issues in code changes by reviewing git diffs targeting working tree, commits, or base refs. Runs read-only and supports structured findings.MIT
- 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