PlugWiki
sentrux logo

sentrux MCP Server: Setup for Claude, Cursor and Other Apps

CommunityLocal

Lets your coding assistant score the structure of your code and see whether its own changes made it better or worse.

sentrux is a Rust app that scans a project and gives it a structural quality score, and its MCP mode lets the assistant use that score. The assistant saves a baseline, makes its changes, and checks whether the score dropped.

It runs on your computer from a single binary. It sends anonymous usage counts unless you turn that off.

Good for

  • Developers using coding agents who worry about code quality drifting
  • Teams who want architecture rules checked during an agent session
  • Reviewers looking for hotspots and untested risky files

Works in

12 should work

Tap an app to see how to set it up and any known problems.

Install sentrux MCP

Claude Code

  1. 1

    Copy this prompt.

    Add the sentrux MCP server to Claude Code. Run this command:
    
    claude mcp add --transport stdio sentrux -- sentrux --mcp
    
    Then check that it loaded and tell me if I need to sign in or restart.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires sentrux installed and on PATH.

Read-only mode: The scoring tools only read. Two tools write local baseline or cache files.

Install sentrux first (Homebrew, the install script on Linux, or a download from GitHub releases for Windows), so the sentrux command is on your PATH. The server is the same program started with --mcp. Claude Code also has a plugin: /plugin marketplace add sentrux/sentrux, then /plugin install sentrux. Run scan first, because the other tools need it. sentrux sends anonymous usage counts and checks for updates once a day unless you run sentrux analytics off.

Built from the package data we hold. Not yet tested by us.

Tools

  • Scans a project and scores its structure

    Reads a folder and computes the structural metrics, then returns an overall quality signal. It has to run before the other tools.

    Try: “Scan my project and tell me its quality signal.”

    Files · scan

  • Explains the quality score

    Returns the quality signal with a breakdown into modularity, acyclicity, depth, equality and redundancy, and names the weakest one.

    Try: “What is dragging down the quality score?”

    Read · health

  • Picks up recent file changes

    Scans the current folder again to include changes since the last scan.

    Try: “Rescan the project after my edits.”

    Files · rescan

  • Saves a quality baseline

    Remembers the current metrics in memory so they can be compared after the assistant has made changes.

    Try: “Save a baseline before you start coding.”

    Read · session_start

  • Compares quality to the baseline

    Scans again and shows whether the structure got better or worse since the baseline.

    Try: “Did my changes make the structure worse?”

    Read · session_end

  • Checks architecture rules

    Tests the constraints in .sentrux/rules.toml and returns pass or fail with the violations. The README says some builds check only a few rules unless you have a paid plan.

    Try: “Do we break any architecture rules?”

    Read · check_rules

  • Shows which files change the most

    Analyzes Git history for churn, hotspots, bus factor and files that change together. It returns raw data, not a score. It is listed as evolution in the README.

    Try: “Which files are the riskiest hotspots?”

    Read · git_stats

  • Shows file dependencies as a matrix

    Builds a matrix of how files depend on each other, with clusters and inversions.

    Try: “Show me the dependency matrix of this project.”

    Read · dsm

  • Finds risky files without tests

    Cross-checks test files, imports and complexity to list high-risk source files with no test coverage.

    Try: “Which risky files have no tests?”

    Read · test_gaps

Read from the source code

Permissions

low risk · 1 thing to watch

Low risk

The tools read your project and Git history, and nothing changes your code. The app sends anonymous usage counts and checks for updates daily unless you turn it off.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • Sends anonymous usage counts

    The source says it pings once a day with counts such as scans and tool calls, and checks for updates. Run sentrux analytics off to stop it. github.com

Security advisories

No published security advisories as of Nov 1, 2026.

Technical details
Talks toapi.sentrux.dev for update checks and anonymous usage counts
Sign-in and keysNo sign-in. A license tier may limit some tools.
Scopes
  • Files in the folder you scan

Questions

Is sentrux official?

It is the project's own MCP mode, from the sentrux repository. It is not made by an IDE or language vendor.

Does it need an account or key?

No. Some features may be limited by license tier. The source mentions a Pro tier.

Can it change my code?

No. The tools read your project and Git history. The session baseline is kept in memory while the server runs.

Does it send data?

It sends anonymous usage counts and checks for updates once a day. Run sentrux analytics off to stop that.

How do I install it?

Install sentrux with Homebrew, the Linux script or a Windows download, then add the server as in the install box.

Why is the tool called git_stats and not evolution?

The README says evolution, but the source registers it as git_stats. The page follows the source.

Information

updated Nov 2, 2026

Publisher
Community
Transport
stdio
Auth
None
License
MIT
Last commit
Mar 19, 2026
Open issues
26

WebsiteGitHubChangelogIssues

Sources

Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.

Show all 4
  1. handlers_evo.rs · github.com
  2. README.md · github.com
  3. handlers.rs · github.com
  4. update_check.rs · github.com

Facts from the official MCP registry, GitHub, npm, PyPI and the Docker catalog. Updated Nov 2, 2026.