What it does
mergelock is aimed at conflicts that git cannot see when branches are combined. The publisher's example is a function signature changed on one branch while a new caller of that function appears on another. Git merges both changes without complaint, so the clash only shows up in the code. Developers working with MCP-compatible tools might use it while combining branches in a development workflow. The source gives no details on setup, supported languages or how results are reported.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
mergelock
Finds merge conflicts git can't see between branches: changed signatures vs new callers.
v0.1.5As shown on registry.modelcontextprotocol.io when we last read it