← Back to directory
P

Project Health Auditor

Community
Analyze local repos for code health, complexity, test coverage gaps
GitHub source repository ↗
★ 2.7k Stars Category · Dev Tools Very popular Source revision 3277af5249f0
21FMRS · D
Reliability
3/20
Security and permissions
5/20
Maintenance
5/20
Documentation
3/20
Setup experience
5/20

This server is part of the Claude Code plugin marketplace and provides local code health analysis. Functionality is straightforward, but specific analysis algorithms and tools are not disclosed; actual capabilities need validation.

Read the FMRS scoring method →

Project Health Auditor is an MCP server that analyzes local code repositories for code health, complexity, churn, and test coverage gaps to identify technical debt hotspots. It provides multi-dimensional health analysis to help developers focus on areas needing attention.

Tools

The tool list has not been reviewed yet.

Setup

To install this MCP server:

  1. Install the CLI globally using npm: pnpm add -g @intentsolutionsio/ccpi (or use npm).
  2. Run ccpi install project-health-auditor to install the plugin.

Alternatively, use Claude Code's built-in command: /plugin install project-health-auditor@claude-code-plugins-plus.

Fit and risk

Best for

  • Development teams maintaining medium to large codebases
  • Developers wanting to assess code health before refactoring
  • Engineering managers needing quantified code risk to plan tech debt cleanup

Not for

  • Scenarios requiring deep security auditing
  • Real-time monitoring of production environments
  • Analysis of non-local repositories

Required permissions

  • Read local repository filesystem
  • Analyze code statistics

Risks and side effects

  • Potential misclassification of some code patterns as high complexity
  • Analysis results depend on local repo state and may become stale
  • Analysis of large repositories may be time-consuming

Troubleshooting

  1. Ensure npm package is correctly installed and version matches
  2. Check that local repository path is correct
  3. Verify network connectivity if external resources are required
  4. Inspect MCP server logs to diagnose errors

Use cases

Evaluate complexity distribution across a codebase
Identify modules with insufficient test coverage
Locate technical debt hotspots

Supported clients

Claude DesktopFull support