Server data from the Official MCP Registry
Plan stale and merged branch cleanup: keep / review / delete per branch, with reasons.
About
Plan stale and merged branch cleanup: keep / review / delete per branch, with reasons.
Security Report
gitcleanplan is a pure local computation that classifies git branches as keep, review, or delete from caller-supplied data, with no network access, no file reads beyond the input, no git invocation, and no deletions; it only lists safe-delete commands. Input validation is strict and path-naming, and the MCP server exposes a single tool with an explicit schema. No security findings of concern were identified; the only observations are minor and informational. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 2 high severity). Package verification found 1 issue.
8 files analyzed · 6 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Required
This plugin requests these system permissions. Most are normal for its category.
How to Install
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-cloudcorprecords-gitcleanplan": {
"args": [
"-y",
"@reneturcios/gitcleanplan"
],
"command": "npx"
}
}
}Documentation
View on GitHubFrom the project's GitHub README.
gitcleanplan
Branch lists grow quietly. A feature lands, its branch stays; an experiment is abandoned, its branch stays too; the upstream disappears and the local copy lingers. Deleting branches on a hunch is how work gets lost, so gitcleanplan takes the middle road: you hand it the branch data, and it hands back a plan — lists first, deletes nothing.
For every branch you supply, the plan gives one of three decisions, each with the reason that produced it:
- keep — the default branch, a protected branch, the branch currently checked out, or a branch that is simply still active.
- review — merged but recently active, upstream gone but not merged, or stale but not merged: promising cleanup candidates that deserve a human look before anything else.
- delete — merged and either its upstream is gone or
it has been stale for at least
stale_days. Only merged branches can ever land here.
Decisions follow a fixed rule order, so the reason is never
ambiguous: the default branch wins over protection,
protection wins over a merged-and-gone branch, being checked
out wins over being merged, and "merged and upstream is
gone" wins over "merged and stale". Staleness is inclusive —
a branch whose last commit was exactly stale_days ago
counts as stale.
Alongside the per-branch decisions, the result groups the
branch names under each action, counts them, and lists one
safe-delete command (git branch -d <name>) per branch
planned for deletion, in name order. Those commands are
listed, never run: gitcleanplan does not invoke git,
open a repository, or delete anything. You read the plan,
and you decide what to execute yourself.
Malformed input — a missing or empty branch list, a missing,
empty, or duplicated branch name, a missing, negative, or
non-integer last_commit_days_ago, a wrongly typed flag, a
bad stale_days or default_branch — is a validation error
naming the offending path (for example
branches[1].last_commit_days_ago must be an integer >= 0),
and no partial plan is produced. The computation is pure and
local: no network, no configuration, no files read beyond
the input you pass in.
CLI
npx @reneturcios/gitcleanplan plan --input args.json
npx @reneturcios/gitcleanplan --version
args.json contains the full arguments object:
{
"stale_days": 90,
"branches": [
{ "name": "main", "last_commit_days_ago": 0, "current": true },
{ "name": "shipped-feature", "merged": true, "upstream_gone": true, "last_commit_days_ago": 45 },
{ "name": "old-spike", "last_commit_days_ago": 180 }
]
}
merged, upstream_gone, protected, and current
default to false per branch; stale_days defaults to
90; default_branch defaults to "main". The plan is
printed as JSON:
{
"branches": [
{ "name": "main", "action": "keep", "reason": "default branch" },
{ "name": "old-spike", "action": "review", "reason": "stale but not merged" },
{ "name": "shipped-feature", "action": "delete", "reason": "merged and upstream is gone" }
],
"plan": {
"delete": ["shipped-feature"],
"review": ["old-spike"],
"keep": ["main"]
},
"counts": { "delete": 1, "review": 1, "keep": 1 },
"commands": ["git branch -d shipped-feature"]
}
Exit codes: 0 on success, 1 on a runtime error (including
an unreadable or invalid input file, or invalid input), 2
on a usage error.
MCP server
npx -y @reneturcios/gitcleanplan mcp
MCP client config:
{
"mcpServers": {
"gitcleanplan": {
"command": "npx",
"args": ["-y", "@reneturcios/gitcleanplan", "mcp"]
}
}
}
Tools
-
plan_branch_cleanup— Plan stale and merged branch cleanup.branches(array, required, at least one) — branches as{name, last_commit_days_ago, merged?, upstream_gone?, protected?, current?}objects;nameis unique across the set andlast_commit_days_agois a whole-day count of at least 0stale_days(integer, optional, default 90, at least 1) — a branch is stale at this many days since its last commitdefault_branch(string, optional, default"main") — the default branch name; it is never planned for deletion
Returns
{branches, plan, counts, commands}.
Docker
docker run -i ghcr.io/cloudcorprecords/gitcleanplan
docker run --rm -v "$PWD:/w" ghcr.io/cloudcorprecords/gitcleanplan plan --input /w/args.json
Development
npm install
npm run build # tsc -> dist/
npm test # tsx --test test/*.test.ts (pure local, no network)
npm run dev # run the CLI from source
License
MIT — Copyright (c) 2026 Rene Turcios
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Rea
Freeby Morluto · Developer Tools
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Paperclip
Freeby Paperclipai · Developer Tools
Trending hip-hop artist momentum scores across four cultural dimensions.
Fetch
Freeby Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
