Claude Code Guardian

What is Claude Code Guardian?

Claude Code Guardian is an MCP server providing 113+ AI-safe code analysis tools for Claude Code and other MCP clients. It includes guard modules for code validation, persistent memory, task workflows, automated testing, code optimization, multi-phase reasoning, and session management.

How to use Claude Code Guardian?

Install globally with npm install -g codeguardian-studio, then add the server configuration to your Claude Desktop config. The server is invoked via npx -y codeguardian-studio as an MCP command.

Key features of Claude Code Guardian

• 20+ code validation rules (fake tests, empty catch, security issues)
• Persistent knowledge storage across sessions
• Task tracking with progress dashboard
• Automated test runner plus browser testing with Playwright
• Hotspot detection, complexity analysis, and refactoring plans
• Multi-phase reasoning for complex tasks
• Auto-save, resume, and session checkpoints

Use cases of Claude Code Guardian

• Enforce code quality and security rules during AI‑assisted development
• Maintain persistent project context across multiple Claude sessions
• Track and manage development tasks with visual progress
• Automate test execution and browser-based end-to-end testing
• Analyze code complexity and generate refactoring plans

FAQ from Claude Code Guardian

What runtime does Claude Code Guardian require?

It requires Node.js and is installed as a global npm package (codeguardian-studio).

How is Claude Code Guardian configured for Claude Desktop?

Add the server entry to the mcpServers object in the Claude Desktop configuration file, using npx -y codeguardian-studio as the command.

Does Claude Code Guardian support other MCP clients?

Yes, the README states it works with Claude Code and other MCP clients.

How many tools does Claude Code Guardian offer?

The server provides 113+ tools for code analysis, testing, workflow, and session management.

What data does the memory module store?

Persistent knowledge is stored across sessions, but the README does not specify storage location or retention limits.