Ext Ops Panel
Open dashboard
Comparison

resolve-merge-conflicts vs com.gitkraken/gk-cli

resolve-merge-conflicts is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑23.

resolve-merge-conflicts is a plugin bundle for AI coding tools published by iowarp. No marketplace we read lists it any more. com.gitkraken/gk-cli is an MCP server published by gitkraken.com. Marketplaces we read that list it: 3 (Official MCP Registry, Claude Code: claude-plugins-official, Claude: knowledge-work-plugins). As of our marketplace pass on 2026-10-26. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceresolve-merge-conflictscom.gitkraken/gk-cli
Community marketplace iowarp/clio-kit Removed on 2026-10-16
Version: 0.4.0
Forks (GitHub): 5
Stars (GitHub): 8
Not marked · First seen
Not listed
Community marketplace iowarp/clio-coder Removed on 2026-10-23
Version: 0.4.1
Forks (GitHub): 5
Stars (GitHub): 8
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 3.1.77
Downloads/month (npm): 106 261
Downloads/week (npm): 23 741
Forks (GitHub): 375
Stars (GitHub): 461
Not marked · First seen
Claude Code: claude-plugins-official Not listed Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Claude: knowledge-work-plugins Not listed Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

resolve-merge-conflicts vs com.gitkraken/gk-cli
Factresolve-merge-conflictsno longer listed · com.gitkraken/gk-cli
Marketplaces that list it (differs)03
Stars (GitHub) (differs)8461
Forks (GitHub) (differs)5375
Last release (differs)Not published2026-10-14
Where it runs (differs)Installs as a plugin bundleOn your machine (@gitkraken/gk)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not published1
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/iowarp/clio-codergithub.com/gitkraken/gk-cli
Changes in the last 7 days (differs)60
First seen (differs)2026-10-132026-10-11

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of resolve-merge-conflicts

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • GenPark Git Semantic Cherry-Pick Conflict Resolver

    Three-way AST hunk alignment and non-overlapping block conflict resolution for Git cherry-picks

    by alphaparkinc · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • clash

    Detect merge conflicts across git worktrees before they happen. Warns before writing to files that would cause merge conflicts when running multiple AI agents in parallel.

    by Clash Contributors · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • git-workflow-expert

    Git branching strategies, conflict resolution, rebase workflows, monorepo patterns, and advanced operations like cherry-pick, bisect, and reflog recovery. Activate on "git…

    by curiositech · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • gitwand io.github.devlint/gitwand

    Auto-resolves Git merge conflicts so agents only touch the complex hunks.

    by devlint · MCP server

    Listed on: Official MCP Registry, npm registry (MCP servers) · Describes nearly the same job

  • git-workflow-expert

    Git strategies, merge conflicts, and advanced version control expert

    by DevsForge Community · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • mergelock

    Finds merge conflicts git can't see between branches: changed signatures vs new callers.

    by sadayamuthu · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

resolve-merge-conflicts

In its own words, on Community GitHub marketplaces:

Resolves a merge, rebase, or cherry-pick stopped on conflicts by reconstructing both sides' intent, validating with the project's own checks, and completing the operation. Not for integrating many branches; use worktree-merge.

com.gitkraken/gk-cli

In its own words, on Official MCP Registry:

The GitKraken MCP Server for managing repos, PRs, issues across GitHub, GitLab, Bitbucket and more.

How to run each

resolve-merge-conflicts

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

com.gitkraken/gk-cli As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio gk-cli -- npx -y @gitkraken/gk mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: resolve-merge-conflicts · What it can do: com.gitkraken/gk-cli · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built