CodeHealth MCP Server
CodeHealth MCP Server is a local quality gate that makes AI coding assistants fix maintainability issues before you approve the code.
If AI is writing a meaningful share of your diffs, this is the most direct quality gate you can bolt onto the workflow — the agent gets told what to fix instead of you finding it in review. The token-spend and defect-risk numbers are the commercial argument. Skip it if nobody on the team is using an AI assistant yet.
Verified 4d ago · liveness 74/100 · cite: rightaichoice.com/tools/codehealth-mcp-server
- Engineering teams already running AI coding assistants who need a maintainability guardrail
- Platform teams enforcing one CodeHealth standard across AI-generated code from many tools
- Organizations with large legacy codebases they want to make AI-friendly before scaling agents
- Teams that must prove refactoring ROI on velocity, defect rates, and maintenance costs
- Teams not using MCP-compatible AI assistants or agents, where the server has nothing to gate
- Anyone wanting a general-purpose AI code generator rather than a quality check on one
- Groups that prefer entirely manual code review with no automated feedback loop
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip CodeHealth MCP Server if nobody on your team runs an MCP-compatible AI assistant yet — the server has nothing to gate until agents are writing a meaningful share of your diffs.
Pricing counts active authors, so every developer touching gated repositories adds €18/mo Standard or €27/mo Pro, billed yearly.
Standard at €18/active author/mo billed yearly and Pro at €27/active author/mo billed yearly sit in the mid-range for code-quality platforms: cheaper than SonarQube-style enterprise governance suites, more expensive than a free linter. The per-active-author model makes CodeScene expensive for large teams but predictable for small ones; Enterprise is custom-quoted for orgs running millions of lines across global teams.
In short
CodeHealth MCP Server — CodeHealth MCP Server is a local quality gate that makes AI coding assistants fix maintainability issues before you approve the code. Best for Engineering teams already running AI coding assistants who need a maintainability guardrail, Platform teams enforcing one CodeHealth standard across AI-generated code from many tools, Organizations with large legacy codebases they want to make AI-friendly before scaling agents. Free to start; paid plans from €18/mo.
What's new in CodeHealth MCP Server
Checked 4 days agoAcross the latest 5 updates: 1 feature update and 4 changelog entries.
Release Notes 7.5.12
Reduces memory usage related to loading PR results during full analysis. Docker, JAR and on-prem builds available.
Release Notes 7.5.11
Adds Azure support to the PR Refactoring Agent and GitHub Apps authentication for on-prem installations. Also fixes TypeScript readonly T[] parameters being silently excluded from Code Health analysis.
Release Notes 7.5.10
Fixes a false positive Bumpy Road warning for Python and missing Code Insights report updates in the Bitbucket Server PR integration.
Release Notes 7.5.9
Blocks API users from creating projects outside their group, adds Azure DevOps work item to pull request links, and supports local Git remotes on-prem.
Release Notes 7.5.8
Masks Git provider tokens in the configuration UI. JAR download available for direct installs.
Viability Score
How well maintained and how widely used is CodeHealth MCP Server? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: October 2026
How we score →Key Features
- Real-time CodeHealth checks on AI-generated changes
- Self-correcting feedback loop until maintainability thresholds are met
- Deterministic PR Refactoring Agent triggered from GitHub and GitLab pull requests
- Azure support added to the PR Refactoring Agent in CodeScene 7.5.11 (September 2026)
- Quality gate that blocks risky AI changes before approval
- Runs locally on your machine for full data privacy and control
- Model-agnostic—works with any MCP-compatible AI assistant or agent
- Supports 30+ programming languages
- Token usage optimization—up to 45% lower token spend
- AI agents fix 2–5x more Code Health issues when guided by the MCP server
- Component hotspot code health badges for high-risk areas
- PR checks run 30–90% faster with fewer git operations during concurrent analyses
- /active-authors API endpoint for active authors across projects
- Git provider tokens masked in the configuration UI (CodeScene 7.5.8)
- ROI impact reporting on velocity, defect rates, and maintenance costs
About CodeHealth MCP Server
CodeHealth MCP Server is CodeScene's MCP-based quality gate for AI-generated code. It runs locally on your machine, plugs into any MCP-compatible assistant, and checks each AI change against CodeScene's CodeHealth signals. When risk goes up, the server returns structured feedback so the agent adjusts and retries until maintainability thresholds are met — a deterministic self-correcting loop rather than a hope-for-the-best review. It is built for engineering teams scaling agentic coding, not for solo tinkerers. Vendor benchmarks cite MCP-guided agents fixing 2–5x more Code Health issues, healthy code correlating with 60% lower defect risk, and up to 45% lower token spend — a real cost line once agents are writing a large share of your diffs. What you get in practice: real-time CodeHealth checks on any AI-generated change, deterministic PR Refactoring Agents that trigger guided refactorings from pull requests in GitHub and GitLab — Azure support was added to the PR Refactoring Agent in CodeScene 7.5.11 (September 2026) — component hotspot badges for high-risk areas, and support for 30+ programming languages. Recent releases have sped up PR checks by 30–90% through fewer concurrent git operations, masked Git provider tokens in the configuration UI, and added an /active-authors API endpoint. It is model-agnostic by design — GitHub Copilot, Cursor, Claude Code, ChatGPT, Codeium, Windsurf and others via MCP — and ROI reporting ties refactoring to velocity, defect rates and maintenance costs. Compared with general-purpose linters, this targets the maintainability properties that determine whether agents succeed, not just syntactic rules.
Behind the Verdict
The pitch is narrow and that is its strength: CodeHealth MCP Server does not write code, it refuses to let bad code through. Install it locally, point your MCP-compatible assistant at it, and every change gets checked against CodeScene's CodeHealth signals. If risk rises, the server hands structured feedback back to the agent, which retries. CodeScene funds one 2026 case study — loveholidays — showing a move from 0 to 50% agent-assisted code in five months while holding quality. Strengths: it runs on your machine, so regulated and privacy-sensitive teams keep source in-house. It is model-agnostic, so a team running Copilot on one repo and Claude Code on another gets one standard. The PR Refactoring Agent is deterministic rather than generative — it triggers guided refactorings from a pull request in GitHub, GitLab, and (as of 7.5.11 in September 2026) Azure. Vendor numbers worth noting: 2–5x more Code Health issues fixed by MCP-guided agents, 60% lower defect risk on healthy code, up to 45% lower token spend, and 30–90% fewer git operations during concurrent PR checks after the 7.5.2 improvement. Weaknesses: this is an early-access product and it is a dependency, not a standalone tool — no MCP-compatible assistant means nothing to gate. It provides no generative capability of its own. The per-active-author model (€18/mo Standard, €27/mo Pro, both billed yearly) scales with headcount, so a 200-developer org is a real line item. Quality gates fail for files under an already-reached refactoring goal, but 7.5.1 fixed that class of issue; expect more rough edges around newer surfaces like the PR Refactoring Agent. Where it fits: platform teams standardising one CodeHealth bar across many AI tools; organisations with large legacy codebases that want code made AI-friendly before scaling agents; anyone who needs to prove refactoring ROI on velocity, defect rates and maintenance costs. Where it does not: solo developers who do not run an MCP assistant, teams that want a generator rather than a gate, and buyers expecting live multi-user collaborative editing.
Researching CodeHealth MCP Server? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Real-world workflow fit
Concrete scenarios for the personas CodeHealth MCP Server actually fits — and what changes day-one when you adopt it.
Install the MCP server locally on each developer machine, configure it against CodeScene Standard, and let Cursor's agent check every generated change against CodeHealth signals before the developer accepts it.
Outcome: Risky AI diffs get corrected during authoring rather than surfacing in review, and the platform team sees one maintainability bar across every repo instead of per-tool rules.
Turn on the PR Refactoring Agent for GitHub pull requests and let it trigger one-click refactorings on the highest-risk functions before agents are allowed to work in that area.
Outcome: Legacy hotspots get restructured through normal review, making the codebase AI-ready before broader agent rollout.
Track token spend before and after enabling CodeHealth checks, using the server's feedback loop to stop agents from looping on unhealthy files.
Outcome: Up to 45% lower token spend per vendor benchmarks, with component hotspot badges showing where the remaining waste sits.
Use Cases
- Guide Claude Code or Copilot to fix Code Health issues during development
- Automatically review pull requests for technical debt before merge
- Refactor legacy codebases with agentic assistance and quality checks
- Enforce maintainability standards across AI-generated code
- Monitor token consumption and reduce waste by improving code health
- Assess AI risk and scale AI coding safely within enterprise guardrails
Models Under the Hood
as of 2026-09-23
Limitations
- The CodeHealth MCP Server is an early-access product.
- It requires an MCP-compatible AI assistant to function—it's not a standalone code analyzer you run in CI.
- Pricing is per active author (€18–27/month billed yearly), which can add up for large teams.
- The server focuses on code health signals and does not provide generative AI capabilities of its own.
- Some features like the PR Refactoring Agent are newer (June 2026) and may have rough edges—Azure support only landed in 7.5.11 in September 2026.
as of 2026-10-05
Verification history
We have re-verified CodeHealth MCP Server 9 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-checked, vendor evidence unchanged
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
Showing the 6 most recent of 9 verification passes.
Free to cite with attribution — this page re-verifies continuously.
12-month cost
Project the real annual outlay, including the implied monthly cost when only an annual tier is published.
Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.
Plans compared
For each published CodeHealth MCP Server tier: who it actually fits, and what it adds vs. the previous tier. Cross-reference the cost calculator above for projected annual outlay.
Community Edition
$0
Ideal for
Open-source maintainers who want CodeHealth analysis on a public project without paying anything.
What this tier adds
Free entry point — analysis and community support for open-source projects only.
CodeHealth MCP Server Package
€86/yr
Ideal for
A single developer who wants to trial the MCP quality gate on their own machine before rolling it out to a team.
What this tier adds
Standalone €86/yr package with a 14-day no-credit-card trial, real-time CodeHealth checks on AI changes, and deterministic refactoring feedback.
Standard
€18/active author/mo (billed yearly)
Ideal for
An engineering team already running AI assistants that needs a maintainability gate and unlimited private repositories.
What this tier adds
Adds the CodeHealth deterministic score, the MCP Server, the PR Refactoring Agent, fully automated code review, and 30+ language support versus the free and package tiers.
Pro
€27/active author/mo (billed yearly)
Ideal for
A multi-team engineering org that needs portfolio-level visibility and delivery metrics, not just per-repo checks.
What this tier adds
Everything in Standard plus software portfolio overview, team and delivery insights, and code coverage measurement.
Enterprise
Custom
Ideal for
Large regulated organisations running millions of lines of code across global teams that need governance and dedicated onboarding.
What this tier adds
Everything in Pro plus SSO with role-based access control, a dedicated Customer Success Manager, tailored onboarding and workshops, and CodeHealth KPIs across teams.
CodeScene ACE (add-on)
Contact sales
Ideal for
Teams staring down large legacy functions that need to be restructured before agents can safely work in them.
What this tier adds
Separate add-on, quoted through sales — an AI-refactoring agent in the IDE that auto-fixes technical debt before it enters the codebase.
Where the pricing makes sense
The company stage and team size where CodeHealth MCP Server's pricing actually pencils out — and where peers do it cheaper.
Standard at €18/active author/mo billed yearly and Pro at €27/active author/mo billed yearly sit in the mid-range for code-quality platforms: cheaper than SonarQube-style enterprise governance suites, more expensive than a free linter. The per-active-author model makes CodeScene expensive for large teams but predictable for small ones; Enterprise is custom-quoted for orgs running millions of lines across global teams.
Setup time & first value
How long it actually takes to get something useful out of CodeHealth MCP Server — broken out by persona, not the marketing-page minute.
Solo developer on an MCP-compatible assistant: 15–30 minutes to install the server locally and point the assistant at it — the 14-day trial needs no credit card. Team rollout: a day or two per repository to wire in Git provider authentication, configure quality gates and agree CodeHealth thresholds. Enterprise with on-prem: add time for database setup (MySQL 8.4 with mysql-native-password=ON) and
Switching to or from CodeHealth MCP Server
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From manual PR review only: install the MCP server locally, connect it to your existing assistant, and let the quality gate run alongside human review before you remove any steps.
- →From SonarQube: keep SonarQube for syntactic rules and add CodeHealth checks on the diff, since CodeScene positions CodeHealth as 6x more accurate on maintainability signals than static analysis.
- →From a standalone linter in CI: add the MCP server so agents get feedback during authoring, then keep the linter for the rules it still covers.
- ↗To plain SonarQube: you keep rule-based linting but lose the agent feedback loop, PR Refactoring Agent, and CodeHealth scoring.
- ↗To GitHub-native code scanning: you get repo-integrated alerts but no deterministic refactoring from pull requests and no per-author CodeHealth trend.
- ↗To doing nothing: your agents keep generating code with no maintainability gate, and review catches the debt instead.
Integrations
Resources & Guides
Tutorials & Learning
YouTube returned 6 videos for “CodeHealth MCP Server”, and we withheld 6: 6 did not mention CodeHealth MCP Server. We are showing none, because we could not prove any of them are about CodeHealth MCP Server.
Official links
Tools that pair well with CodeHealth MCP Server
Common stack mates teams adopt alongside CodeHealth MCP Server, with the specific reason each pairing earns its keep.
Qodo
AI code review and governance that gives your coding agents a quality counterpart.
Skylos
Skylos is a local-first Python static analysis CLI that catches dead code, secrets, and AI-code mistakes before they merge.
Bito
Bito Governor is an AI model router and code context engine that grounds coding agents in your codebase to cut agent spend 40-70%
Featured Head-to-Head Comparisons
Codehealth Mcp Server vs Spider Cloud
If your pain point is technical debt and code quality from AI-generated code, CodeHealth MCP Server is your must-have – it provides deterministic feedback to prevent unhealthy code and reduces token waste. If your need is ingesting live web data for AI agents or RAG pipelines, Spider Cloud’s fast Rust engine, 99.9% success rate, and low cost per page make it the clear choice. Choose based on whether you need to fix code or fetch data.
Codehealth Mcp Server vs Temporal Ai
Choose CodeHealth MCP Server if your priority is enforcing code quality and reducing technical debt in AI-generated code; it excels at real-time, deterministic feedback for AI coding assistants. Opt for Temporal AI if you need a robust durable execution platform for managing long-running workflows and AI agents with automatic retries and state persistence. They solve different problems: quality vs. reliability.
Codehealth Mcp Server vs Voyage Ai
Choose CodeHealth MCP Server if your team uses AI coding assistants and wants to prevent technical debt in real time with deterministic quality gates. Choose Voyage AI if your priority is building high-accuracy RAG pipelines with domain-specific embeddings and long-context support. They solve fundamentally different problems — code quality vs. retrieval accuracy — so the decision hinges on your primary challenge. For most teams, CodeHealth offers immediate value with a freemium tier, while Voyage requires enterprise commitment.
Alternatives to CodeHealth MCP Server
View all
Frequently Asked Questions
Used CodeHealth MCP Server? Help shape our editorial sentiment research.