Tech Debt MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_projectA | Analyze an entire project for technical debt. Scans all supported files and returns a comprehensive report with issues, metrics, and recommendations. |
| analyze_fileA | Analyze a single file for technical debt issues. |
| get_debt_summaryA | Get a quick summary of technical debt in a project. |
| get_sqale_metricsB | Get SQALE technical debt metrics including remediation time, debt ratio, and rating. |
| list_supported_languagesA | List all programming languages supported by the analyzer. |
| get_recommendationsA | Get prioritized recommendations for addressing technical debt. |
| get_issues_by_severityB | Get all issues of a specific severity level. |
| get_issues_by_categoryB | Get all issues of a specific category. |
| add_custom_ruleA | Add a custom pattern-based tech debt rule. |
| remove_custom_ruleA | Remove a custom rule by ID. |
| list_session_custom_rulesA | List custom rules registered in this server session via add_custom_rule. Does NOT include customPatterns declared in .techdebtrc.json (those run inside analyze_project via AnalysisEngine but are not surfaced here). Renamed from list_custom_rules (TEC-51) for clarity; the old name is no longer registered. |
| execute_custom_rulesA | Execute all custom rules against code or a file. |
| validate_custom_patternA | Validate a custom pattern before adding it as a rule. |
| check_dependenciesB | Analyze project dependencies across multiple package managers. |
| validate_configA | Validate a .techdebtrc.json configuration file for syntax and schema correctness. |
| get_vulnerability_reportA | Generate an offline dependency report listing all project dependencies for vulnerability review. Note: actual CVE lookups require Phase 2b online integration. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
Each tool has a distinct purpose. analyze_file vs analyze_project differ by scope. get_issues_by_category and get_issues_by_severity filter differently. Custom rule tools (add, remove, list, execute) are clearly separate actions. No overlapping functionality.
All tool names follow a consistent verb_noun pattern in snake_case. Verbs like add, analyze, check, execute, get, list, remove, validate are used predictably. No mixing of conventions.
16 tools is slightly above the typical 3-15 range, but each tool serves a clear purpose for tech debt analysis. The count is reasonable for the domain and does not feel excessive.
The tool surface covers analysis, custom rules, metrics, filtering, recommendations, and config validation. Minor gaps: get_vulnerability_report is offline only (no actual CVE lookup), and there is no tool for tracking debt over time. Otherwise complete for its purpose.