codehealth-mcp

原文涵盖的主题

• Code Health MCP (CodeScene)
• Security and boundaries
• When to Use
• When to Activate
• How It Works
• 1. Connect the MCP server
• 2. Call standalone tools only
• 3. Interpret scores (1–10)

Structural maintainability feedback for AI-assisted coding. Complements style/lint skills (coding-standards, plankton-code-quality) with design-level health scores and regression gates. Upstream: codescene-oss/codescene-mcp-server Package: @codescene/codehealth-mcp (stdio via npx) Opt-in (ECC): The codescene block in mcp-configs/mcp-servers.json is a template only. ECC plugin installs do not auto-enable bundled MCP servers. Copy the entry into your config only if you want it. You can exclude it during ECC install/sync with ECCDISABLEDMCPS=codescene,.... Credentials: No bundled token. Set CSACCESSTOKEN yourself (see getting-a-personal-access-token.md in the upstream repo). Never commit tokens to the repo. What the tools read: When invoked, tools analyze files and git state in the local repository you point them at (paths you pass, plus branch context for analyzechangeset). They do not run by themselves. For standalone mode, follow upstream privacy docs: codescene-mcp-server README and CodeScene policies. Do not use this skill for secrets, credentials, or paths you do not want analyzed. If the MCP is unavailable (offline, bad token, server crash): Do not invent Code Health scores. Te

这里只展示节选，请以完整原文和当前要求为准。