
Approvepath
io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 3, 2026
Map who must approve a PR: CODEOWNERS rules plus who actually reviews these files.
Overview
Approvepath's local MCP server; no sign-in required; STDIO.
No AI overview yet: these facts come from the registry entry and the server itself.
Installation
In SourceWeft
- Open Approvepath in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
approvepath
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.
CLI
args.json contains the full arguments object:
reviews is optional and defaults to []. The result is
printed as JSON:
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
MCP client config:
Tools
-
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}, wherepatternis a non-empty string andownersis 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}, whererevieweris a non-empty string andfilesis an array of strings (may be empty)
Returns
{files, unowned_files, required_reviewers}, wherefilesholds one{file, owners, pattern, frequent_reviewers}entry per changed file, in input order.
Docker
Development
License
MIT — Copyright (c) 2026 Rene Turcios
Source: README.md at commit 511d783
Tools
0Version history
1- v0.1.0LatestNov 3, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts