branch-closeout vs GitEasy MCP
branch-closeout is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑23.
branch-closeout is a plugin bundle for AI coding tools published by iowarp. No marketplace we read lists it any more. GitEasy MCP is an MCP server published by greenmtnsun. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-13. 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 |  GitEasy MCP | |
|---|---|---|
| Community marketplace iowarp/clio-kit | Removed on 2026-10-16 Version: 0.1.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.1.1 Forks (GitHub): 5 Stars (GitHub): 8 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.6.2 Forks (GitHub): 0 Stars (GitHub): 1 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 | branch-closeoutno longer listed · | GitEasy MCP |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 8 | 1 |
| Forks (GitHub) (differs) | 5 | 0 |
| Last release (differs) | Not published | 2026-10-25 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (giteasy-mcp.azurewebsites.net/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| 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/greenmtnsun/giteasy |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 19 h ago, requires authentication |
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 branch-closeout
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Safely analyzes and cleans up local git branches and worktrees by categorizing them as merged, squash-merged, superseded, or active work.
-
Audits, preserves and recovers local Git state before cleanup: unpushed or wrong-branch commits, dirty worktrees, duplicate clones, stashes, dangling commits, squash-merge…
-
Git worktree management for parallel development workflows
-
Git worktree workflow commands for task-based development
-
Post-merge cleanup after a PR is merged on GitHub: syncs main, removes the merged worktree and branch, and watches CI/CD. Worktree-aware.
-
Replaces Claude Code's built-in worktree — aligns with native git worktree where CC diverges (HEAD base, origin/* auto-tracking) and adds layers native lacks…
What each says it does
branch-closeout
Proves merged work on the canonical base, inspects and removes associated worktrees through Git, deletes local branches safely, and audits surviving repository refs. Not for creating worktrees; use worktree-create. Not for integrating branches; use worktree-merge.
GitEasy MCP
Plain-English git for agents: 22 tools to branch, commit, push and tag. Free tier.
How to run each
branch-closeout
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
GitEasy MCP As a remote MCP server
claude mcp add --transport http giteasy https://giteasy-mcp.azurewebsites.net/mcp --header "X-Api-Key: <YOUR_X_API_KEY>"Requires: X-Api-Key header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only GitEasy MCP has a remote endpoint we check. How we check endpoints
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: branch-closeout · What it can do: GitEasy MCP · 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.