Simple Merge Review MCP
Provides tools for Git merge analysis, including showing changes between branches and quick merge change summaries.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Simple Merge Review MCP Show changes between main and feature/login"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Simple Merge Review MCP
A lightweight MCP server for quick Git merge analysis. Shows only essential information without complex conflict checks.
🚀 Features
Quick Merge Overview - core change statistics
Changed Files List - what will be affected by merge
Simple Statistics - number of commits, lines, files
Related MCP server: MCP Merge Request Summarizer
📦 Installation
# Clone the repository
git clone <repository-url>
cd local-merge-review-mcp
# Install dependencies
npm install
# Build the project
npm run build🛠️ Just 2 Simple Tools
1. show_merge_diff
Show changes between branches before merge.
await mcp.call_tool("show_merge_diff", {
repoPath: "/path/to/your/repo",
fromBranch: "main", // optional, defaults to main
toBranch: "feature/new-feature" // optional, defaults to current
});Result:
{
"sourceBranch": "main",
"targetBranch": "feature/new-feature",
"filesChanged": ["src/component.js", "package.json", "README.md"],
"insertions": 45,
"deletions": 12,
"commits": 3,
"summary": "3 commits, 3 files, +45/-12 lines"
}2. quick_merge_summary
Quick merge change summary.
await mcp.call_tool("quick_merge_summary", {
repoPath: "/path/to/your/repo",
branch: "feature/auth" // optional, defaults to current
});Result:
{
"currentBranch": "feature/auth",
"baseBranch": "main",
"message": "5 commits ahead",
"aheadBy": 5,
"behindBy": 0,
"needsMerge": true
}📋 Common Use Cases
Quick Pre-merge Check
"Show changes in feature/payment branch compared to main"
# show_merge_diffBranch Status Check
"How many commits ahead is the current branch?"
# quick_merge_summaryUnderstanding Change Scope
"How many files will change after merging this branch?"
# show_merge_diff + file list analysis📝 Usage with Claude Example
"Show changes between main and feature/auth in /home/user/myproject"
"How many commits ahead is current branch from main?"
"Which files will change after merge?"⚡ Why Simple is Better
Fast - no complex conflict checks
Clear - only essential information
Reliable - minimal dependencies
Practical - covers 90% of use cases
By default, conflicts are not expected, so complex checks are unnecessary. This MCP shows only what's truly important before merging.
⚠️ Requirements
Git installed and available in PATH
Node.js >= 18.0.0
🚧 Easy to Add Features
Format handling for specific files (.js, .py, etc)
Package.json version integration
Basic metrics (lines of code, comments)
Export to various formats
Available Tools
3 toolsquick_merge_summaryB
Quick summary of changes for merge
Inputs: repoPath (required), branch.
show_file_diffB
Show specific changes in a file between branches
Inputs: repoPath (required), filename (required), fromBranch, toBranch.
show_merge_diffA
Show changes between branches before merge
Inputs: repoPath (required), fromBranch, toBranch.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a clear, distinct purpose: one provides a summary, one shows diffs for a specific file, and one shows the overall diff between branches. There is no overlap or ambiguity.
All tools use snake_case and start with a descriptive term. However, 'quick_merge_summary' uses an adjective, while the others use a verb, creating a slight inconsistency in pattern.
With only 3 tools, the server is well-scoped for its purpose of simple merge review. Each tool is essential and nothing seems unnecessary or missing.
The tools cover the core needs for merge review: a summary, overall diff, and file-level diff. Minor features like listing changed files or branch management are not present but are not essential for the minimal scope.
Maintenance
Related MCP Connectors
Risk-scan a diff, flag AI-generated-code tells, find secrets. 5 of 7 tools need no account.
Generate SBOMs, scan vulnerabilities, and analyze dependencies from local projects or Git repos.
Screens public GitHub repos and PRs to generate risk maps, findings, and merge-readiness signals.
Merget for coding agents: set up the merge queue, operate it, and read its findings and code graphs.
Related MCP Servers
- AlicenseBqualityDmaintenanceA specialized MCP server for in-depth analysis of git repositories, offering tools for branch overview, time period analysis, file changes, and merge recommendations.47Apache 2.0
- AlicenseNot gradedqualityDmaintenanceAutomatically generates comprehensive merge request summaries from git logs, analyzing commit history and categorizing changes into structured descriptions. Provides tools to analyze git repositories, compare branches, and create detailed summaries with change categorization, impact analysis, and review time estimates.1MIT
- AlicenseNot gradedqualityDmaintenanceA local, read-only Git change review tool that provides total workspace diffs, staged/unstaged views, file-level inspection, and task-scoped snapshots for MCP-compatible clients like Codex, Claude Code, and Cursor.MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to turn local git history into answers about recent activity, file hotspots, change coupling, stale or already-merged branches, contributors, ref comparisons, and drafted release notes. It runs locally over stdio with a git subcommand allowlist, so it is read-only, works offline and without shell access, and is safe to auto-approve.1363 npmMIT