Labsco
MCP SERVER

TechDebtMCP

by PierreJanineh

Puts a number on technical debt — SQALE remediation time, debt ratio and an A-E rating — across fourteen languages and ten dependency ecosystems.

Code Intelligence & Repository IndexingVerified
Summary
It scores the debt rather than only listing it, which turns 'this code is messy' into an argument about priorities.

SQALE remediation time and a debt ratio give the conversation a unit, and recommendations come back already ranked. Two boundaries worth knowing: the dependency report lists what your project pulls in for review rather than looking up CVEs, and custom rules added during a session are tracked separately from the customPatterns declared in .techdebtrc.json.

What it is

A static analyser behind an MCP interface. It scans a project for debt, scores it, and returns issues you can slice by severity, category or language rather than one undifferentiated list.

What you get
  • analyze_project across a whole tree, filtered by severity, category or language and capped with maxFiles; analyze_file for a single file; get_debt_summary for the short version
  • SQALE metrics: remediation time, debt ratio and an A-E rating, with your development time as an input
  • Issues sliced the way you want to read them — by severity or by category — and a prioritised recommendation list
  • Language-specific checks across JavaScript, TypeScript, Python, Java, Swift, Kotlin, Objective-C, C++, C, C#, Go, Rust, Ruby and PHP: force unwraps and retain cycles in Swift, bare excepts in Python, ignored errors in Go, unwrap and unsafe in Rust, empty catches in Java and C#, and so on
  • Specialised SwiftUI checks for state management, view nesting, memory leaks and concurrency
  • Custom rules two ways: registered for the session with a regex, message, severity and category — validated before you add them — or declared as customPatterns in .techdebtrc.json
  • Dependency analysis across npm, pip, Maven and Gradle, Cargo, Go Modules, Composer, Bundler, NuGet, C/C++ and Swift, plus an offline report listing every dependency for review
  • validate_config to check a .techdebtrc.json against the schema instead of discovering the mistake through odd results
  • Inline suppression for genuine false positives with a techdebt-ignore-next-line comment
Requirements

Nothing to authorize — it reads the code you point it at. Run it over stdio with npx -y tech-debt-mcp@latest, or install it as a Claude Code plugin, or as an MCPB bundle for Claude Desktop that ships its dependencies and needs no network at runtime. Behaviour comes from a .techdebtrc.json in the project root: include and ignore globs, thresholds for file length, function length, complexity and nesting depth, per-rule severity overrides, per-path rule exclusions, and custom regex patterns.

Setup effort

One command — npx -y tech-debt-mcp@latest