mcpField
M
merge-conflict-forecaster-mcp

merge-conflict-forecaster-mcp

Local
github.com/mrfentmenVersion Control

About merge-conflict-forecaster-mcp

Predict local Git merge-conflict pressure from branch topology and changed-file overlap without...

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"mrfentmen-merge-conflict-forecaster": {
"command": "npx",
"args": [
"-y",
"merge-conflict-forecaster-mcp"
]
}
}
}
Run commandnpx -y merge-conflict-forecaster-mcp

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmmerge-conflict-forecaster-mcp1.0.0

Tools

1

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
cwdstringNoLocal Git repository path inside the configured workspace; no network access is used.
basestringNoOptional local branch name used as the comparison base.
limitintegerNoMaximum number of local branches to analyze.

Details

The maintainer has not added details yet. Check the README in the repository.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.