Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Map who must approve a PR: CODEOWNERS rules plus who actually reviews these files.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"approvepath": {
"command": "npx",
"args": [
"-y",
"@reneturcios/approvepath",
"mcp"
]
}
}
}在终端中运行这条命令
claude mcp add approvepath -- npx -y @reneturcios/approvepath mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"approvepath": {
"command": "npx",
"args": [
"-y",
"@reneturcios/approvepath",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"approvepath": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/approvepath",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 CloudCorpRecords 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.1.0)于3天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js, Docker。
同一分类中有:Spec Driven Development, Remote Desktop Commander, debuff
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Let coding agents play, test and tune your 2D web game: live state, explained errors, replays, fuzz.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
A CODEOWNERS file says who is *supposed* to approve a change. Review history says who *actually* shows up. approvepath puts the two side by side for one pull request: you hand it the CODEOWNERS rules, the files the PR touches, and whatever past review activity you have, and it hands back, per file, the owners the rules assign and the people who have reviewed that exact file before.
Pattern matching follows a pinned subset of CODEOWNERS semantics, so the answer never depends on which CODEOWNERS dialect you had in mind. Any leading / is stripped from both the pattern and the file path before comparing. A pattern ending in / is a directory prefix: it matches every file under that directory. A pattern containing * is a glob that must match the whole path — ** matches any run of characters including /, while a single * matches any run except /. Any other pattern matches a file that equals it exactly, or a file underneath it (the pattern plus / as a prefix), so a bare directory name owns its whole subtree.
When several rules match the same file, the last matching rule in file order wins — the same override rule CODEOWNERS itself uses, and the reason a broad early rule can hand a subtree to a team while a later, narrower rule hands one corner of it back. A file no rule matches is unowned: its owners list is empty and its pattern is null, and it also appears in unowned_files, in input order.
Review history is counted plainly. For each changed file, frequent_reviewers counts, per reviewer, how many supplied review entries by that reviewer list the file exactly — no prefix credit, no directory credit. Reviewers are ranked by count descending, then by name ascending, and only the top three are reported. required_reviewers collects every owner from every winning rule across the PR, deduplicated and sorted, which is the shortest honest answer to "whose approval does this PR actually need?".
Everything is computed locally from the arguments alone: no repository is read, no hosting API is called, and nothing is guessed. Malformed input — a rule with an empty pattern, a changed file that is not a non-empty string, a review entry missing its reviewer — is a validation error naming the offending path, with no partial result.
npx @reneturcios/approvepath map --input args.json
npx @reneturcios/approvepath --version
args.json contains the full arguments object:
{
"codeowners": [ { "pattern": "src/", "owners": ["@core"] }, { "pattern": "src/api/", "owners": ["@api-team", "sam"] } ], "changed_files": ["src/api/handler.ts", "README.md"], "reviews": [ { "reviewer": "sam", "files": ["src/api/handler.ts"] }, { "reviewer": "lee", "files": ["src/api/handler.ts"] } ] }
reviews is optional and defaults to []. The result is printed as JSON:
{
"files": [ { "file": "src/api/handler.ts", "owners": ["@api-team", "sam"], "pattern": "src/api/", "frequent_reviewers": [ { "reviewer": "lee", "reviews": 1 }, { "reviewer": "sam", "reviews": 1 } ] }, { "file": "README.md", "owners": [], "pattern": null, "frequent_reviewers": [] } ], "unowned_files": ["README.md"], "required_reviewers": ["@api-team", "sam"] }
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.
npx -y @reneturcios/approvepath mcp
MCP client config:
{
"mcpServers": { "approvepath": { "command": "npx", "args": ["-y", "@reneturcios/approvepath", "mcp"] } } }
map_approvals — Map the approval path for a pull request.codeowners (array, required, may be empty) — CODEOWNERS rules in file order; each entry is {pattern, owners}, where pattern is a non-empty string and owners is an array of non-empty strings (may be empty)changed_files (array of strings, required, non-empty) — paths of the files the PR changesreviews (array, optional, default []) — past review activity; each entry is {reviewer, files}, where reviewer is a non-empty string and files is an array of strings (may be empty)Returns {files, unowned_files, required_reviewers}, where files holds one {file, owners, pattern, frequent_reviewers} entry per changed file, in input order.
docker run -i ghcr.io/cloudcorprecords/approvepath
docker run --rm -v "$PWD:/w" ghcr.io/cloudcorprecords/approvepath map --input /w/args.json
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
MIT — Copyright (c) 2026 Rene Turcios