Code Auditor Mcp
Run SOLID, DRY, and broader code-quality audits from your IDE via MCP before you merge or ship indie SaaS changes.
Overview
Code Auditor MCP is a MCP server for the Ship phase that analyzes code for SOLID principles, DRY violations, and related quality issues over stdio from npm.
What is this MCP server?
- Code Quality Auditor MCP for SOLID principles and DRY violation detection
- npm package code-auditor-mcp at version 2.0.2 with stdio transport
- Broader quality signals beyond a single linter rule set
- Fits pre-merge agent-assisted review in Claude Code or Cursor
- GitHub-maintained BenAHammond/code-auditor-mcp project
- npm package version: 2.0.2
- Transport: stdio
- Registry identifier: code-auditor-mcp on registry.npmjs.org
Community signal: 6 GitHub stars.
What problem does it solve?
Indie builders merge fast without a consistent architecture review, so SOLID and DRY debt piles up unnoticed until refactors block shipping.
Who is it for?
Solo developers who want agent-triggered craftsmanship checks during Ship review without configuring a heavyweight static-analysis portal.
Skip if: Greenfield ideas with no code yet, or teams that need licensed security penetration testing instead of design-principle audits.
What do I get? / Deliverables
After you add the npm stdio server to your agent, you get on-demand quality audits in the IDE before merge or deploy.
- Agent-invoked quality audit reports for target files or repos
- SOLID and DRY violation findings surfaced in the IDE workflow
- Repeatable pre-ship review step without leaving the coding agent
Recommended MCP Servers
Journey fit
Quality and architecture review belong in Ship when code is written and you gate releases—not while you are still sketching ideas. Code Auditor analyzes existing code for principles and violations—canonical shelf is Ship → review alongside pre-release checks.
How it compares
MCP code-quality reviewer, not a payment MCP or team wiki knowledge graph.
Common Questions / FAQ
Who is Code Auditor MCP for?
Solo and indie builders using Claude Code, Cursor, or Codex who want MCP-driven SOLID and DRY feedback on code they are about to ship.
When should I use Code Auditor MCP?
Use it in Ship review after features are implemented and before you merge, tag a release, or hand code to users.
How do I add Code Auditor MCP to my agent?
Install code-auditor-mcp from npm at 2.0.2, add a stdio MCP server entry pointing at the package in your client config, then invoke audit tools on your project path from the agent.