Code Guardian
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Code Guardianaudit this project for production readiness and give me my grade"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Code Guardian — Production Readiness Plugin for Claude Code
A Claude Code plugin that enforces production-readiness standards across any project. Audits codebases against industry best practices, checks branch strategy, validates testing and CI/CD setup, and computes a quality scorecard.
Features
Tool | What it does |
| Full audit: linting, TypeScript, testing, CI/CD, docs, dependencies |
| Verifies git branch naming follows conventions (feature/, bugfix/, etc.) |
| Discovers test files/frameworks and runs a quick test execution check |
| Detects CI/CD configs (GitHub Actions, GitLab CI, Jenkins, CircleCI, Docker) |
| Finds installed linters (ESLint, Prettier, Biome, oxlint, stylelint) and runs ESLint |
| Scans for .env leaks and runs |
| Reviews directory structure and monorepo indicators |
| Computes an A–F grade scorecard across 10 quality dimensions |
Related MCP server: Inspectra
Transports
stdio — Runs as a subprocess (Claude Code's default plugin transport)
HTTP/SSE — Listens on
http://localhost:8765for direct MCP protocol access
Installation
The plugin is already installed at:
~/.claude/plugins/cache/claude-plugins-official/code-guardian/v1/To install manually:
cp -r ~/.claude/plugins/cache/claude-plugins-official/code-guardian/v1 \
~/.claude/plugins/cache/claude-plugins-official/code-guardian/<version>/Then register it in ~/.claude/plugins/installed_plugins.json.
Usage
Once installed, Claude Code will automatically load the plugin. The tools are available as MCP tools — invoke them directly or ask Claude to run an audit:
"Run code-guardian and audit this project" "Check my production readiness score" "Is my branch naming compliant?" "Run a security scan with npm audit"
Project structure
code-guardian/
├── .claude-plugin/
│ └── plugin.json # Plugin manifest (name, description, author)
├── .mcp.json # MCP server config (stdio + HTTP transports)
├── package.json # Node.js package
└── src/
├── tools.js # All tool implementations (shared)
├── stdio-server.js # stdio entry point for Claude Code
└── http-server.js # HTTP/SSE entry point (port 8765)Extending
Add a new tool by:
Implementing the function in src/tools.js
Adding it to the
TOOLSarray and dispatch switch in src/stdio-server.js and src/http-server.jsUpdating
.mcp.jsonif a new transport config is needed
This server cannot be deployed
Maintenance
Related MCP Connectors
Free MCP tools: the only MCP linter, health checks, cost estimation, and trust evaluation.
Read-only AI coding tools for change verification, release readiness, capacity, and guidance.
Statically audits MCP tool surfaces for token cost, schema quality, and design issues.
AI-native git hosting — repos, PRs, issues, CI gates, and AI code review over MCP (60 tools).
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI coding environments to enforce engineering governance through MCP tools and resources for init, check, route, and review workflows.82MIT
- AlicenseNot gradedqualityCmaintenanceEnables hybrid code audits using MCP tools across 12 domains, producing structured, scored, and actionable code quality reports.101MIT
- AlicenseAqualityBmaintenanceA local-first MCP server that scores your codebase's Build Readiness by reading code and running tests on your machine, outputting a diligence-grade score and risk register without uploading your source.577Apache 2.0
- AlicenseAqualityCmaintenanceEnables agents to audit and safeguard repositories by detecting dependency pinning issues, license compliance problems, hardcoded secrets, and dead code through MCP tools.4MIT