Codescene Mcp Server
Expose CodeScene Code Health findings to your agent so refactors and PR reviews target real complexity and hotspot risk.
Overview
CodeScene MCP is an MCP server for the Ship phase that exposes CodeScene Code Health analysis tools to coding agents over stdio.
What is this MCP server?
- stdio MCP package @codescene/codehealth-mcp on npm (server manifest version 0.3.1)
- CodeScene Code Health analysis tools exposed to the agent
- GitHub-hosted open-source server (codescene-oss/codescene-mcp-server)
- Server schema version 1.1.0 in registry metadata
- Fits agent-assisted review loops without replacing human judgment
- Registry server version 1.1.0
- npm package @codescene/codehealth-mcp version 0.3.1
- Transport: stdio
Community signal: 50 GitHub stars.
What problem does it solve?
Agents guess at refactor priority without objective code-health data, so reviews miss the files that actually drag velocity.
Who is it for?
Builders using CodeScene who want MCP-driven review context in Claude Code or Cursor.
Skip if: Greenfield prototypes with no CodeScene project or teams that only want free lint rules with zero CodeScene footprint.
What do I get? / Deliverables
Your agent can query Code Health signals during review so recommendations align with measured complexity and maintainability risk.
- Agent-callable Code Health analysis queries
- Health-informed review and refactor suggestions in chat
- stdio MCP integration documented in registry v1.1.0
Recommended MCP Servers
Journey fit
Code health analysis belongs in Ship when you harden quality before release, not when you are still sketching product scope. Review is the right shelf because the server surfaces maintainability and health metrics meant to guide code review and pre-merge decisions.
How it compares
Code health MCP bridge to CodeScene, not a standalone linter skill or generic static-analysis CLI.
Common Questions / FAQ
Who is CodeScene MCP for?
Developers and small teams on CodeScene who want AI assistants to use Code Health metrics during review and refactoring conversations.
When should I use CodeScene MCP?
Use it in Ship during code review, release hardening, or debt sprints when you need health-backed prioritization before merge or deploy.
How do I add CodeScene MCP to my agent?
Install @codescene/codehealth-mcp from npm, configure stdio transport in your MCP client, and point it at your CodeScene-connected workspace per the GitHub server README.