LabscoMCP early access ↗
phuongrealmaxMCP SERVER

Claude Code Guardian

Scan a large repository for complexity hotspots, plan the refactor, and keep the session's state across conversations.

by phuongrealmax ↗Code Intelligence & Repository IndexingCommunity

LABSCO SUMMARY

For repositories where the agent needs a map before it starts editing.

The centre of this server is the hotspot pass: scan, score, rank, and only then plan a change. What makes it worth wiring up over a plain analyser is everything around that loop — guard rules that reject fake tests, a session store that lets the same refactor continue in tomorrow's conversation, and a task list that lives in the project rather than in the chat.

What it is

Code Guardian Studio (CCG), a refactoring workbench for a coding agent working on a repository too big to hold in one context. It maps the codebase, scores files by complexity, writes the refactor plan, and remembers where you left off. Version 4.1.0, MIT open-core.

What you get

  • A repository map and a ranked list of what to fix first — code_scan_repository, code_metrics, code_hotspots, or code_quick_analysis for all three in one call
  • A step-by-step plan and a Markdown report you can hand to a human: code_refactor_plan, code_generate_report
  • Guard rules that block dangerous patterns such as fake tests and empty catch blocks — guard_validate, guard_rules, guard_toggle_rule, guard_check_test
  • Work that survives the end of a conversation: session_save, session_resume, session_timeline, session_replay, plus memory_store and memory_recall
  • Task tracking inside the repo — workflow_task_create, workflow_task_start, workflow_task_complete, workflow_task_list, and progress views via progress_status and progress_blockers
  • Semantic code search over an index you build once: rag_build_index, rag_query, rag_related_code
  • Test and browser runs wired in — testing_run, testing_run_affected, testing_browser_open, testing_browser_errors, testing_browser_network
  • One natural-language entry point, ccg_run, which translates a prompt into a tool sequence and can return the plan without executing it
  • 173 tools in the project's tools reference, grouped into agents, AST, guard, latent chain, memory, process, profile, RAG, resource, session, testing, thinking and workflow families

Requirements

Node.js 18.0.0+ and npm 8.0.0+, and the npm package codeguardian-studio — installed globally, or launched with npx. CCG_PROJECT_ROOT is the one required environment variable and must point at your project root; CCG_LOG_LEVEL and CCG_LICENSE_KEY are optional. Running ccg init inside the project writes the client configuration for you. The bundled better-sqlite3 native module compiles at install time, so a build toolchain has to be present: Xcode Command Line Tools on macOS, build-essential and python3 on Debian and Ubuntu, Visual Studio Build Tools on Windows. The Dev plan is free and fully offline; the Team plan is $19/month and validates its licence against api.codeguardian.studio.

Setup effort

One command — npm install -g codeguardian-studio