MCP servers · cloudcorprecords

approvepath: map PR approvers from CODEOWNERS and review history

Maps the approval path for a pull request by comparing CODEOWNERS rules with the past reviewers of each changed file.

This text was machine-translated from the publisher's own information and has not been checked by a human editor. The publisher's original text is the reference.

This resource was imported automatically from the sources listed below and has not been reviewed by the AI Gate team yet. The description is the publisher's own, as published. Check the repository before installing.

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.0
    As shown on registry.modelcontextprotocol.io when we last read it
MCP servers
hashicorp

Terraform MCP Server (HashiCorp)

HashiCorp's MCP server that gives an assistant current Terraform Registry information on providers, modules and policies, and can manage HCP Terraform workspaces.

1.6K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026
MCP servers
neondatabase

Neon MCP Server (Postgres)

Neon's MCP server for managing Neon Postgres in plain language: create projects and branches, run queries and prepare schema migrations from your editor.

663 GitHub starsData & databasesSoftware development
Updated 17 Nov 2026
MCP servers
redis

Redis MCP Server

Redis's official MCP server that lets an AI assistant store, read and search data in a Redis database, including streams, JSON documents and vector indexes.

642 GitHub starsData & databasesSoftware development
Updated 17 Nov 2026
MCP servers
supabase-community

Supabase MCP Server

Supabase's MCP server that connects an AI assistant to your Supabase project to design tables, run queries, read configuration and look up documentation.

Data & databasesSoftware development
Updated 17 Nov 2026