# Technical Debt Ratio Analyzer AI Agent Connect

> Calculates technical debt accumulation and provides strategic investment recommendations.

## Overview
- **Category:** project-management
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_yqjAOGQjXwLW1C4EWaLB7xfJATGDuyblAE3AVFId/ai-agent-connect
- **Tags:** technical-debt, metrics, devops, engineering-intelligence, velocity

## Description

This MCP server provides a specialized analytical engine to monitor technical debt. It calculates the Debt Ratio and Debt Service Time to help teams understand how much capacity is lost to rework. Use `calculate_debt_metrics` to get strategic investment guidance, `get_debt_thresholds` to view configuration constants, `analyze_velocity_trend` to track capacity erosion, and `compare_feature_vs_debt_ratio` to assess overall project health.

## Tools

### analyze_velocity_trend
Evaluates how much the team capacity is being eroded by accumulated debt

### compare_feature_vs_debt_ratio
Compares new work against debt accumulation to determine project health

### calculate_debt_metrics
Calculates primary technical debt indicators and provides strategic recommendations

### get_debt_thresholds
Retrieves configuration constants used to categorize debt levels

## Prompt Examples

**Prompt:** 
```
Calculate my debt metrics for 50 new features, 10 bugs fixed, 20 refactoring hours, 500 total dev hours, and a 5% defect rate.
```

**Response:** 
```
Your debt ratio is 0.04, debt service time is 6%, and the recommendation is Feature Focus with Low velocity impact.
```

**Prompt:** 
```
Compare 100 new features against a debt ratio of 0.15.
```

**Response:** 
```
The project health status is Productive with a productivity index of 6.67.
```

**Prompt:** 
```
What are the current debt thresholds?
```

**Response:** 
```
The low ratio threshold is 0.1, the high service time threshold is 20%, and the critical defect rate is 15%.
```

## Frequently Asked Questions

**What is the primary purpose of this server?**
It quantifies technical debt and provides actionable recommendations for feature development versus refactoring.

**How is the debt service time calculated?**
It is the proportion of total developer hours spent on bugs and refactoring tasks.

**Can I use this to track team velocity?**
Yes, by using `analyze_velocity_trend`, you can evaluate how much capacity is being eroded by accumulated debt.