Techdebtmcp MCP Server

MCP Server for analyzing technical debt across multiple programming languages

Local serverstdioPython

What is the Techdebtmcp MCP server?

Techdebtmcp MCP server exists for a simple reason — assistants are far more useful when they can act on Techdebtmcp directly instead of describing what you should do. MCP Server for analyzing technical debt across multiple programming languages.

What you get

A Model Context Protocol (MCP) server for analyzing technical debt across multiple programming languages. Designed to integrate with GitHub Copilot, Claude, Cursor, and other MCP-compatible tools.

  • Multi-language support — JavaScript, TypeScript, Python, Java, Swift, Kotlin, Objective-C, C++, C, C#, Go, Rust, Ruby, PHP
  • Comprehensive analysis — Detects various types of tech debt including code quality issues, security vulnerabilities, and maintainability problems
  • SQALE Metrics — Calculate technical debt with SQALE rating system (A-E scale)
  • SwiftUI Analysis — Specialized checks for SwiftUI patterns, state management, memory leaks, view nesting, and concurrency issues
  • Custom Rules — Define your own pattern-based checks with regex support
  • Dependency Analysis — Parse package manifests across 10 ecosystems (npm, pip, Maven/Gradle, Cargo, Go Modules, Composer, Bundler, NuGet, C/C++, Swift)

What the assistant can call

Once Techdebtmcp is connected, these are the calls the assistant has available:

  • Category — Tool
  • Analysis — analyze_project
  • Filtering — get_recommendations
  • Dependencies — check_dependencies
  • analyze_project — path
  • analyze_file — path
  • get_debt_summary — path
  • get_sqale_metrics — path
  • get_recommendations — path
  • get_issues_by_severity — path
  • get_issues_by_category — path
  • list_supported_languages — —

Setting it up

tech-debt-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Choosing this one

Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Techdebtmcp's toolset — Category, Analysis, Filtering and 11 more — is a fair guide to whether it matches your workflow. It is maintained by pierrejanineh; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Techdebtmcp.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the techdebtmcp mcp server does with a few real requests.

Available tools

ToolWhat it does
CategoryTool
Analysisanalyze_project
Filteringget_recommendations
Dependenciescheck_dependencies
analyze_projectpath
analyze_filepath
get_debt_summarypath
get_sqale_metricspath
get_recommendationspath
get_issues_by_severitypath
get_issues_by_categorypath
list_supported_languages
add_custom_ruleid
remove_custom_ruleid

How to install the Techdebtmcp MCP server

{
  "mcpServers": {
    "techdebtmcp": {
      "command": "npx",
      "args": ["-y", "tech-debt-mcp"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Example prompts to try

  • Use Techdebtmcp to Category.
  • Use Techdebtmcp to Analysis.
  • Use Techdebtmcp to Filtering.

Frequently asked questions

It connects Techdebtmcp to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (Category, Analysis, Filtering, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Techdebtmcp directly.