Coding Standards
Install an MCP guardrail server so your agent applies DDD, SOLID, and TDD expectations while reviewing or generating production-grade code.
Overview
Coding Standards MCP is an MCP server for the Ship phase that enforces DDD, SOLID, and TDD guardrails while your agent reviews or writes production-grade code.
What is this MCP server?
- Enforces production-oriented standards: DDD, SOLID, and TDD guardrails via MCP
- Published on npm as @corbat-tech/coding-standards-mcp (v1.0.3) with stdio transport
- Keeps architecture and testing expectations in the tool layer instead of brittle chat reminders
- Targets teams and solos who want consistent agent output before merge or deploy
- Developer Tools MCP integration, not a standalone linter binary
- npm package @corbat-tech/coding-standards-mcp version 1.0.3
- Guardrail focus: DDD, SOLID, TDD (per server description)
Community signal: 4 GitHub stars.
What problem does it solve?
Agent-generated patches often ship without clear domain boundaries, SOLID structure, or tests unless you repeat the same lecture every session.
Who is it for?
Solo builders doing pre-ship code review with an MCP client who want DDD/SOLID/TDD enforced on every agent-assisted change.
Skip if: Greenfield prototypes where speed beats structure, or repos that already rely solely on human-only review with no agent involvement.
What do I get? / Deliverables
After adding @corbat-tech/coding-standards-mcp, reviews and refactors pull consistent architecture and TDD expectations from MCP tools instead of fragile prompt memory.
- Agent responses aligned to DDD, SOLID, and TDD expectations during review
- More structured module boundaries in suggested diffs
- Repeatable standards checks without pasting long review checklists into chat
Recommended MCP Servers
Journey fit
Coding standards surface when you are hardening code before release—reviews, refactors, and test discipline—so Ship is the primary journey shelf even if you invoke it during Build. The server enforces architecture and test guardrails during code review and revision, which maps directly to the review subphase rather than greenfield scaffolding.
How it compares
MCP standards enforcement layer, not a hosted SonarQube replacement or a single-repo CLAUDE.md skill file.
Common Questions / FAQ
Who is coding-standards for?
It is for developers using MCP agents who need DDD, SOLID, and TDD guardrails during Ship-phase review and refactoring.
When should I use coding-standards?
Use it before merge or release when you want the agent to align patches with production conventions instead of quick-and-dirty snippets.
How do I add coding-standards to my agent?
Install @corbat-tech/coding-standards-mcp from npm, add a stdio MCP server entry in Claude Code or Cursor pointing at the package binary, and reload the client.