原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Treeman

作者:CloudCorpRecords版本 0.1.0i★ –i在你的电脑上运行
注册名称io.github.CloudCorpRecords/treeman

安装

概览

作者提供的说明(英文原文)

Map parallel-agent git worktrees to owners and plan safe cleanup from supplied facts.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 开发者工具

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

  • 基础检查:1 项中通过 1 项
  • 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
  • 注册中心没有列出需要填写的密钥。

你需要

  • npm已安装 Node.js(用于 npx 命令)

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "treeman": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/treeman",
        "mcp"
      ]
    }
  }
}

在终端中运行这条命令

claude mcp add treeman -- npx -y @reneturcios/treeman mcp

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "treeman": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/treeman",
        "mcp"
      ]
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "treeman": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/treeman",
        "mcp"
      ]
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上,无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 CloudCorpRecords 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

与“开发者工具”中的其他服务器比较i

  • 星标数多于此分类中其他 1385 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 1385 个服务器的 92% 更新
  • 基础检查结果等于或优于此分类中其他 1385 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Treeman 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(0.1.0)于3天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js, Docker。

有什么可以替代它?

同一分类中有:GitHub, Desktop Commander, Cloudflare MCP

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

GitHub

作者:github

Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.

电脑或云端★ 34,245MIT3天前更新
安装

Desktop Commander

作者:wonderwhy-er

MCP server for terminal commands, file operations, and process management

在你的电脑上运行★ 10,225MIT15天前更新
安装

Cloudflare MCP

作者:cloudflare

Cloudflare MCP servers

在云端运行★ 4,446Apache-2.014个月前更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

treeman

When several agents work in the same repository at once, each one usually gets its own git worktree, and after a while nobody remembers which tree belongs to whom, which ones still hold uncommitted work, and which are safe to delete. treeman answers those questions from facts you already have. You supply, for each worktree, its path, the branch checked out in it, who owns it if anyone does, whether it has uncommitted changes, how many days have passed since it last changed, and whether it is locked — plus the inactivity threshold beyond which a tree counts as stale, and optionally the path of the primary tree. treeman hands back the plan: an ownership map, a status and cleanup action for every tree, and the tallies. It never runs git and never touches the filesystem; it plans from the supplied facts only.

Each tree is judged by a fixed set of checks, first match wins. A tree whose path is the supplied main_path is main and is always kept. A locked tree is locked and kept. A dirty tree is blocked and kept — uncommitted changes are never planned away. A tree that is both past the stale threshold and unowned is orphaned, and it is the only kind planned for removal. An owned tree past the threshold is stale and marked for review; a recent tree with no recorded owner is unowned and also reviewed; an owned, recently active tree is active and kept. The staleness comparison is strictly greater-than: a tree whose last activity is exactly stale_days ago is not stale.

Ownership has one pinned judgement call: an owner that is absent, empty, or only whitespace means the tree is unowned, and its owner is reported as null. The owners map in the result lists every other owner with the paths it owns in the order you supplied them, with the owner keys sorted ascending; unowned trees never appear in it. The counts report the total, one tally per status, and removable — how many trees the plan marks remove.

Malformed input — a missing or empty worktree list, a missing, empty, or non-string path or branch, a non-string owner, a missing or non-boolean dirty, a non-boolean locked, a negative or fractional day count, a bad stale_days, or an empty main_path — is a validation error naming the offending path, with no partial result. Two worktrees with the same path are an error naming the duplicated path. Unknown extra fields are ignored.

CLI

npx @reneturcios/treeman plan --input args.json

npx @reneturcios/treeman --version

args.json contains the full arguments object:

{

"worktrees": [ { "path": "/trees/main", "branch": "main", "owner": "alice", "dirty": false, "last_activity_days": 0 }, { "path": "/trees/old-experiment", "branch": "exp/spike", "dirty": false, "last_activity_days": 74 }, { "path": "/trees/agent-2", "branch": "feat/search", "owner": "agent-2", "dirty": true, "last_activity_days": 1 } ], "stale_days": 30, "main_path": "/trees/main" }

The plan is printed as JSON:

{

"worktrees": [ { "path": "/trees/main", "branch": "main", "owner": "alice", "status": "main", "cleanup": "keep", "reason": "primary worktree" }, { "path": "/trees/old-experiment", "branch": "exp/spike", "owner": null, "status": "orphaned", "cleanup": "remove", "reason": "no owner and inactive beyond the stale threshold" }, { "path": "/trees/agent-2", "branch": "feat/search", "owner": "agent-2", "status": "blocked", "cleanup": "keep", "reason": "uncommitted changes present" } ], "owners": { "agent-2": ["/trees/agent-2"], "alice": ["/trees/main"] }, "counts": { "total": 3, "main": 1, "locked": 0, "blocked": 1, "orphaned": 1, "stale": 0, "unowned": 0, "active": 0, "removable": 1 } }

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/treeman mcp

MCP client config:

{

"mcpServers": { "treeman": { "command": "npx", "args": ["-y", "@reneturcios/treeman", "mcp"] } } }

Tools
  • plan_worktrees — Plan parallel-agent git worktrees from caller-supplied worktree facts: the ownership map, each tree's status, and which trees are safe to remove.
  • worktrees (array, required, at least 1 item) — the worktrees to plan, in the caller's order; each item:
  • path (string, required, non-empty) — worktree path
  • branch (string, required, non-empty) — branch checked out in the worktree
  • owner (string, optional) — agent or person who owns the worktree; absent, empty, or whitespace-only means unowned
  • dirty (boolean, required) — whether the worktree has uncommitted changes
  • last_activity_days (integer, required, at least 0) — days since the worktree last changed
  • locked (boolean, optional) — whether the worktree is locked; absent means false
  • stale_days (integer, required, at least 0) — inactivity threshold in days; beyond it a worktree is stale (exactly at it is not)
  • main_path (string, optional) — path of the primary worktree, which is never cleaned up

Returns {worktrees, owners, counts}, where worktrees holds one {path, branch, owner, status, cleanup, reason} per input worktree in input order (owner is null when unowned), owners maps each distinct owner to its paths, and counts is {total, main, locked, blocked, orphaned, stale, unowned, active, removable}.

Docker

docker run -i ghcr.io/cloudcorprecords/treeman

docker run --rm -v "$PWD:/w" ghcr.io/cloudcorprecords/treeman 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

问 PopNx