worktree-create vs Mergetrain
worktree-create is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑16.
worktree-create is a plugin bundle for AI coding tools published by iowarp. No marketplace we read lists it any more. Mergetrain is an MCP server published by yongjip. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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
| Marketplace |  Mergetrain | |
|---|---|---|
| Community marketplace iowarp/clio-kit | Removed on 2026-10-16 Version: 0.6.0 Forks (GitHub): 5 Stars (GitHub): 8 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 3.7.0 Downloads/month (PyPI): 1 830 Downloads/week (PyPI): 376 Forks (GitHub): 2 Stars (GitHub): 5 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
| Fact | worktree-createno longer listed · | Mergetrain |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 8 | 5 |
| Forks (GitHub) (differs) | 5 | 2 |
| Last release (differs) | Not published | 2026-10-18 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (mergetrain) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/iowarp/clio-coder | github.com/yongjip/mergetrain |
| Changes in the last 7 days (differs) | 2 | 7 |
| First seen (differs) | 2026-10-13 | 2026-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 worktree-create
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Effortless git worktrees for parallel development with automatic environment setup
-
Creates git worktrees for all open PRs or specific branches, handling branches with slashes, cleaning up stale worktrees, and supporting custom branch creation for development.
-
Creates git worktrees for all open PRs or specific branches, handling branches with slashes, cleaning up stale worktrees, and supporting custom branch creation for development.
-
A band above the prompt with the git worktrees of the current repo: branch, uncommitted changes, and the count against a limit of 10.
-
Plugin for Git worktree management using @desplega.ai/wts
-
Visualize the active Git repository through worktrees, branches, commits, and optional GitHub pull request context.
What each says it does
worktree-create
Stands up one or more git worktrees for parallel work, each on its own branch with gitignored config copied in, dependencies installed, and a verified health check. Not for merging finished worktrees; use worktree-merge. Not for closeout; use branch-closeout.
Mergetrain
Queue parallel-agent worktree branches, test together, serialize and recover Git pushes.
How to run each
worktree-create
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Mergetrain As a local MCP server: PyPI package
claude mcp add --transport stdio mergetrain -- uvx --python ">=3.10" --from "mergetrain[mcp]==3.7.0" mergetrain mcpCommands 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: worktree-create · What it can do: Mergetrain · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.