Log inSubmit server
MCP Repo Auditor logo

MCP Repo Auditor

Audits Git changes against repository AI rules and returns a compliance table or self-contained HTML report.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install MCP Repo Auditor

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mcp-repo-auditor": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-repo-auditor"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 4 tools correctly (5d ago).

Overview

The mcp-repo-auditor MCP server checks Git changes against repository guidance such as AGENTS.md, CLAUDE.md, .cursorrules, Copilot instructions, Kiro steering, and skills. It reads the selected diff and relevant rule files locally, then returns a Markdown compliance table or writes an HTML report. Use it before committing staged, working-tree, or branch changes, especially when a repository has extensive AI instructions or a large diff.

Use cases

  • Audit staged changes before committing
  • Check working-tree changes against repository instructions
  • Review a branch against its default or named base branch
  • Generate an HTML compliance report for code review
  • Limit an audit to selected files or folders

Key features

  • Checks Git changes against repository AI rules
  • Supports staged, working-tree, and branch audits
  • Filters audits by files, folders, or globs
  • Returns Markdown tables or HTML reports
  • Splits large audits into trackable parts
  • Supports sequential and parallel part processing

Tools4

What MCP Repo Auditor lets your agent do. Expand a tool for its parameters.

Verified live~1.6k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

What it can do

From the 4 tools this server returned when we ran it; 4 declare their own safety hints.

Makes network requests · 1Read-only tools · 4
Network at startup3 connections
Files written at startupNone
Install scriptsprepare
npm provenanceNot published
Package age12 days
Maintainers1

Observed 2026-10-23 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 7d ago via OSV.dev · mcp-repo-auditor (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads658Package downloads in the last 30 days.
Last commit17d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed4Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How MCP Repo Auditor works

What mcp-repo-auditor does

The mcp-repo-auditor MCP server audits repository changes against the instruction files already present in the project. It can discover guidance such as AGENTS.md, CLAUDE.md, .cursorrules, Copilot instructions, Kiro steering files, and skills, while allowing additional rule paths to be supplied. Rules are applied selectively, so guidance intended for one language or file type is not automatically evaluated against unrelated files.

The server supports staged changes, working-tree changes, and the commits on a branch since its base branch. Audits can be narrowed to files, folders, or globs. Results can appear as a Markdown compliance matrix in the conversation or as a self-contained HTML report with verdict counts, findings, source rules, affected lines, and suggested fixes.

This places mcp-repo-auditor in the Developer Tools category for teams that want an AI assistant to check its own code changes against project-specific conventions before review.

How it works

The MCP client starts the server with npx, and the server reads the selected Git diff plus applicable rule files from the repository. It does not require an API key, account, or network connection. On the first audit for a repository, the assistant asks for the preferred output format, an optional HTML report directory, extra rule files, and the base branch used for branch audits. These preferences are stored per repository in ~/.mcp-repo-auditor/preferences.json, outside the repository.

Large changes are divided into parts after the server presents an audit plan. You can run every part sequentially, select particular parts or paths, or request parallel processing when the client can start subagents. audit_status reports completed parts and totals, while the server combines verdicts from parallel work. An incomplete audit remains explicitly incomplete rather than being reported as compliant.

Setup and configuration

Requirements are Node.js 18.17 or newer, Git on PATH, and an MCP client. Installation uses npx -y mcp-repo-auditor; there is no manual download step. Claude Code, Cursor, VS Code, Kiro, Windsurf, and Claude Desktop configuration examples are provided by the project.

Claude Desktop may need MCP_REPO_AUDITOR_ROOT because it does not run inside the repository. Alternatively, the repository path can be included in the request. On Windows, configurations that cannot launch npx directly should invoke it through cmd /c.

Tools and capabilities

The mcp-repo-auditor MCP server exposes four tools:

  • audit_repo_compliance runs an audit or returns the plan for a large change. It accepts the change scope, branch, paths, audit part, parallel mode, extra rule paths, repository path, and report preference.
  • render_compliance_report writes or refreshes the HTML report from the assistant’s findings.
  • audit_status shows which parts have verdicts and the accumulated totals, including the combined result after parallel auditing.
  • configure_audit saves or updates repository-specific preferences.

Markdown output includes one row per file and rule, violations with locations and fixes, the rules considered, counts, and an overall verdict. HTML output includes verdict counts, findings, rule details, and suggested code changes.

Limitations and notes

The server audits the Git snapshot selected when the plan is created. Later edits do not move files between planned parts. Lockfiles, binaries, generated files, and deleted files may be excluded from large-audit parts, and a file may be only partly covered when its content spans multiple parts.

Parallel auditing depends on the MCP client’s ability to start subagents that can use the tools. If that is unavailable, the assistant falls back to sequential processing. Parallel mode can reduce elapsed time but uses more tokens at once. Large changes also take more time and tokens; narrowing the audit by path can reduce that cost.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCP Repo Auditor

mcp-repo-auditor is an MCP server that connects an AI assistant to a local Git repository and its AI instruction files, including AGENTS.md, CLAUDE.md, and .cursorrules. Its main tools audit repository compliance, render HTML reports, show audit status, and save repository-specific audit preferences without network access.

Install it through your MCP client with `npx -y mcp-repo-auditor`; no manual download is required. The README provides configuration examples for Claude Code, Cursor, VS Code, Kiro, Windsurf, and Claude Desktop.

Yes, mcp-repo-auditor works with Cursor through a `command` of `npx` and arguments containing `-y` and `mcp-repo-auditor` in the Cursor MCP configuration file. The configuration can be global or workspace-specific.

Yes, large changes are divided into parts after the server presents a plan. You can audit parts sequentially, select specific parts or paths, or use parallel subagents when the MCP client supports them; `audit_status` reports progress and combined totals.

No, it does not require an API key, account, or network calls. The server reads the selected Git diff and applicable rule files locally; Node.js 18.17 or newer and Git on `PATH` are required.

Related MCP servers

All in Version Control All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCP Repo Auditor AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mcp-repo-auditor?style=directory)](https://allmcps.com/mcp/mcp-repo-auditor)
HTML Embed
<a href="https://allmcps.com/mcp/mcp-repo-auditor"><img src="https://allmcps.com/api/badge/mcp-repo-auditor?style=directory" alt="MCP Repo Auditor on AllMCPs" /></a>