# Annotation Extractor and Tracker MCP for AI Agents MCP

> Annotation Extractor and Tracker finds the hidden technical debt buried in your source code. It scans for markers like FIXME, HACK, or XXX so you don't miss critical maintenance tasks. You can track how these annotations change over time to see if your team is actually resolving issues or just piling them up.

## Overview
- **Category:** productivity
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_nHleEt0kiJbddwhLdQrs3DvrA6lGbLjDFQwwasod/mcp
- **Tags:** annotation-tracking, code-quality, technical-debt, fixme, hack

## Description

The Annotation Extractor and Tracker MCP lets you manage technical debt by scanning your source files for intentional markers. Managing a codebase means dealing with the messy notes developers leave behind. We all use markers like FIXME or HACK to flag things that need attention later, but those notes often get buried under new commits. This changes how you handle that debt by letting your AI agent actually see and track those markers across your entire project. Instead of manually searching through files, you can ask your agent to find specific issues or check if a previous problem has been fixed. It turns passive comments into actionable data. When you connect this to the Vinkius catalog, you get a direct bridge between your codebase's maintenance needs and your AI client's ability to act on them. You can monitor annotation density to see which parts of your project are becoming unstable or identify exactly when a critical task was finally resolved.

## Tools

### process_annotations
Compares multiple files at once to see which annotations were resolved or added. This helps you track progress over time.

### scan_file
Looks through a single file to find any TODO, FIXME, HACK, or XXX markers. It is useful for targeted audits.

## Prompt Examples

**Prompt:** 
```
Are there any FIXME notes in the auth controller?
```

**Response:** 
```
I found 2 FIXME annotations in `src/controllers/auth.ts`:

* **Line 42**: Fix memory leak
* **Line 89**: Update validation logic
```

**Prompt:** 
```
Did we resolve any HACK markers since my last check?
```

**Response:** 
```
Yes, 3 HACK markers in `src/utils/parser.js` have been resolved since the previous scan.
```

**Prompt:** 
```
Show me where the most annotations are located in the /src folder.
```

**Response:** 
```
The highest density is in `/src/engine`, with 5 annotations, followed by `/src/api` with 2.
```

## Capabilities

### Find hidden technical debt
Scans your files for markers like FIXME and HACK.

### Track maintenance progress
Compares current scans against previous ones to see what was resolved.

### Monitor code quality trends
Identifies where annotations are clustering in your project.

### Audit specific files
Inspects individual files for TODO or XXX tags.

## Use Cases

### Finding pending tasks during refactoring
A developer is refactoring a module and asks the agent to find all FIXME notes in /src/auth. The agent uses scan_file and lists every pending task.

### Verifying bug fix completion
A tech lead wants to see if recent commits fixed old issues. They ask the agent to compare scans, and it uses process_annotations to report resolved markers.

### Identifying code rot in directories
An engineer is worried about code rot in a specific directory. They ask for an annotation density report, and the agent identifies clusters of HACK tags.

## Benefits

- Stop missing critical fixes by using scan_file to find every FIXME in a file.
- Measure progress by using process_annotations to see which tasks were resolved since the last scan.
- Identify high-risk code areas by tracking annotation density across your project.
- Keep your codebase clean by surfacing HACK and XXX markers automatically.
- Automate maintenance audits without manual searching or grep commands.

## How It Works

The bottom line is you stop losing track of critical code fixes.

1. Connect your AI client to the MCP via Vinkius.
2. Point your agent toward a specific file or directory in your repository.
3. Review the extracted list of annotations and their resolution status.

## Frequently Asked Questions

**How can I find all TODOs using Annotation Extractor and Tracker?**
You just ask your agent to scan a specific file or directory for you.

**Can Annotation Extractor and Tracker help me track technical debt?**
Yes, it tracks markers like FIXME and HACK so you can see how they change over time.

**Does Annotation Extractor and Tracker work with my existing codebase?**
It works with any source files where you use standard annotations like TODO or XXX.

**Can I see if a specific bug fix was completed using Annotation Extractor and Tracker?**
Yes, by comparing recent scans to previous ones, the agent can identify resolved markers.

**Is there a way to monitor code quality with Annotation Extractor and Tracker?**
You can check annotation density to find areas of your code that are accumulating too many HACK or FIXME tags.

**What types of annotations can this server detect?**
It detects standard markers including `FIXME`, `HACK`, and `XXX` annotations.

**How can I identify if a task has been completed?**
By using the `process_annotations` tool with a reference from a previous scan, you can see which annotations are now resolved.

**Can I analyze a single file or an entire directory?**
You can use `scan_file` for individual files or `process_annotations` to handle batch data for multiple files.