What it does
approvepath compares two sources for a pull request: the owners that CODEOWNERS rules assign to each changed file, and the people who have reviewed that exact file in past review activity. For each file it returns the owners from the last matching rule, or marks the file as unowned, along with up to three frequent reviewers. It also lists the combined owners across the pull request as required reviewers.
It suits checking whose approval a pull request needs, or seeing who has reviewed a given file before. Pattern matching follows a fixed subset of CODEOWNERS semantics, so results do not depend on which CODEOWNERS dialect is in use. All computation runs locally from the supplied arguments: no repository is read and no hosting API is called.
It runs as a CLI that reads an args.json file and prints JSON, with exit code 0 for success, 1 for runtime errors and 2 for usage errors. It also runs as an MCP server exposing a map_approvals tool, which takes codeowners rules, changed_files and optional reviews, and returns files, unowned_files and required_reviewers.
Limitations and requirements
Malformed input, such as a rule with an empty pattern, a changed file that is not a non-empty string, or a review entry without a reviewer, causes a validation error with no partial result. Frequent reviewers are limited to the top three per file. Review history is only what the caller supplies.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
io.github.CloudCorpRecords/approvepath
Map who must approve a PR: CODEOWNERS rules plus who actually reviews these files.
v0.1.0As shown on registry.modelcontextprotocol.io when we last read it