Semamerge
Catches the merge conflicts Git misses by comparing abstract syntax trees across branches. Exposes four tools: check_merge_safety for quick pre-merge risk scoring, analyze_branches for full three-way semantic diffs, list_semantic_changes to see what actually changed in function signatures and exports, and analyze_file_pair for diving into specific files. Works on TypeScript and JavaScript codebases by parsing with tree-sitter, extracting types and interfaces and function signatures, then cross-referencing changes to find incompatibilities like a branch removing an export while another branch imports it, or one branch changing a return type while another branch depends on the old shape. Runs via stdio without checking out branches.
- tools
- 4
- transport
- STDIO
- last updated
- Apr 25, 2026
Tools
4 toolsPublic tool metadata for what this MCP can expose to an agent.
check_merge_safetyQuick pre-merge check. Returns a risk score (safe/warning/danger).
Quick pre-merge check. Returns a risk score (safe/warning/danger).
No parameter schema in public metadata yet.
analyze_branchesDeep analysis with per-file breakdown of all semantic conflicts.
Deep analysis with per-file breakdown of all semantic conflicts.
No parameter schema in public metadata yet.
list_semantic_changesLists all semantic changes on a branch (functions, exports, types, etc.).
Lists all semantic changes on a branch (functions, exports, types, etc.).
No parameter schema in public metadata yet.
analyze_file_pairDeep-dive into a specific file's semantic diff between two branches.
Deep-dive into a specific file's semantic diff between two branches.
No parameter schema in public metadata yet.
Sponsors
Agent CaffeineSponsoredClose your lid, come back to finished work
SnugSponsoredThe clipboard manager for the AI eraPromote your product hereReach 125k+ visitors monthly
WaxSponsoredBlock anything with supervision, without erasing your iPhonePromote your product hereReach 125k+ visitors monthly
knobsSponsoredSee your site on any phone, any day, in any languageReadme
SemaMerge
An MCP (Model Context Protocol) server that detects semantic merge conflicts between Git branches using AST-level analysis.
When two branches change code in ways that Git merges cleanly but are functionally incompatible, SemaMerge catches it before the merge breaks your app.
What It Detects
Details
- Repository
- github.com/vineethwilson15/semamerge
- Category
- Developer Tools
- Package
semamerge- Transport
- STDIO
- Registry
- MCP registry, active
Related Developer Tools MCP servers
View all
bounty-mcpweiseer/bounty-mcpLive coding-bounty deal-flow from verified-escrow GitHub bounties for AI agents.0stars
ci-triagewjddidi-1/ci-triageGroup failed GitHub Actions runs by root cause; separate real regressions from flaky failures.0stars
Atlassian Dc Mcp Bitbucketb1ff/atlassian-dc-mcpMCP server for Atlassian Bitbucket Data Center - interact with repositories and code108stars
Vscode Terminal Mcpsirlordt/vscode-terminal-mcpExecute commands in visible VSCode terminal tabs with output capture and session reuse.1stars
Git Mcp Servercyanheads/git-mcp-serverComprehensive Git MCP server enabling native git tools including clone, commit, worktree, & more.245stars