Test Coverage MCP

🚀 Test Coverage MCP

Make your agents coverage-aware as they code for you. This project provides an MCP server that offers instant, reliable, and token-efficient test coverage data for any programming language (LCOV based), helping coding and testing agents overcome various challenges in test coverage.

🚀 Just launched (November 2025) ! I spend great time these days on polishing this library. If you find this valuable, a ⭐ star helps signal to other developers that this project is worth their attention

🚀 Quick Start

When AI coding agents work on your code without proper coverage tooling, they face critical issues. This MCP server provides a solution by offering coverage awareness, token efficiency, accuracy, and baseline tracking. Just install it and configure it in your AI coding tools to start using it.

✨ Features

• Coverage Awareness: Agents can check coverage anytime with a simple tool call.
• Token Efficiency: Get coverage summaries in <100 tokens instead of thousands.
• Accuracy: Production - grade LCOV parsing that handles all format variations.
• Baseline Tracking: Measure coverage progress within a session without keeping state in memory.
• High Test Coverage: This project maintains 95% test coverage and aims for 100% soon.

📦 Installation

npm install -g test-coverage-mcp

💻 Usage Examples

Basic Usage

Check Coverage Before Starting Work

Agent: "Let me check the current test coverage before I start working"
[Uses coverage_summary tool]
Agent: "Current coverage is 87.5% lines and 82.1% branches. I'll aim to maintain or improve this."

Advanced Usage

Track Coverage Impact During Development

Agent: "I'll record the baseline coverage first"
[Uses start_recording tool]

Agent: "Now I'll add the new authentication feature with tests"
[Writes code and tests]

Agent: "Let me check the coverage impact"
[Uses get_diff_since_start tool]
Agent: "Great! Coverage increased by 2.3% for lines and 1.8% for branches."

Verify Specific File Coverage

Agent: "Let me check coverage for the file I just modified"
[Uses coverage_file_summary with filePath: "src/auth/validator.ts"]
Agent: "The validator.ts file now has 95% line coverage and 92% branch coverage."

Code Examples

Query Coverage Summary

// Get overall project coverage
coverage_summary({ lcovPath: "./coverage/lcov.info" });
// Returns: { linesCoveragePercentage: 87.5, branchesCoveragePercentage: 82.1 }

// Get coverage for specific files
coverage_file_summary({
  lcovPath: "./coverage/lcov.info",
  filePath: "src/utils/parser.ts",
});
// Returns: { path: "src/utils/parser.ts", linesCoveragePercentage: 92.0, branchesCoveragePercentage: 88.5 }

Baseline Tracking for Session Progress

// At session start - record current coverage as baseline
start_recording({ lcovPath: "./coverage/lcov.info" });
// Returns: "Recording started"

// ... agent writes code and tests ...

// Check coverage impact
get_diff_since_start({ lcovPath: "./coverage/lcov.info" });
// Returns: { linesPercentageImpact: +2.3, branchesPercentageImpact: +1.8 }

📚 Documentation

Configuration

Claude Desktop (Claude Code)

macOS: Edit ~/Library/Application Support/Claude/claude_desktop_config.json Windows: Edit %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "test-coverage": {
      "command": "npx",
      "args": ["-y", "test-coverage-mcp"]
    }
  }
}

After updating, restart Claude Desktop.

Cursor IDE

Create or edit .cursor/mcp.json in your project root:

{
  "mcpServers": {
    "test-coverage": {
      "command": "npx",
      "args": ["-y", "test-coverage-mcp"]
    }
  }
}

GitHub Copilot (VS Code)

Create or edit .vscode/mcp.json in your workspace:

{
  "servers": {
    "test-coverage": {
      "command": "npx",
      "args": ["-y", "test-coverage-mcp"]
    }
  }
}

Requires VS Code 1.99+ or Visual Studio 17.14+. Enterprise users need "MCP servers in Copilot" policy enabled.

Windsurf (Codeium IDE)

macOS: Edit ~/.codeium/windsurf/mcp_config.json Windows: Edit %APPDATA%\Codeium\Windsurf\mcp_config.json Linux: Edit ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "test-coverage": {
      "command": "npx",
      "args": ["-y", "test-coverage-mcp"]
    }
  }
}

Or use the GUI: Settings → Advanced Settings → Cascade → Add Server

Available Tools

coverage_summary

Get overall project coverage from an LCOV file. Input:

{
  lcovPath?: string  // Optional. Defaults to "./coverage/lcov.info"
}

Output:

{
  linesCoveragePercentage: number,      // 0-100
  branchesCoveragePercentage: number    // 0-100
}

Example:

coverage_summary({ lcovPath: "./coverage/lcov.info" });
// { linesCoveragePercentage: 87.5, branchesCoveragePercentage: 82.1 }

coverage_file_summary

Get coverage for a specific file. Input:

{
  lcovPath?: string,  // Optional. Defaults to "./coverage/lcov.info"
  filePath: string    // Required. Path to the file
}

Output:

{
  path: string,
  linesCoveragePercentage: number,      // 0-100
  branchesCoveragePercentage: number    // 0-100
}

Example:

coverage_file_summary({
  lcovPath: "./coverage/lcov.info",
  filePath: "src/utils/parser.ts",
});
// { path: "src/utils/parser.ts", linesCoveragePercentage: 92.0, branchesCoveragePercentage: 88.5 }

start_recording

Record current coverage as a baseline for later comparison. Input:

{
  lcovPath: string; // Required. Path to LCOV file to record
}

Output:

"Recording started";

Example:

start_recording({ lcovPath: "./coverage/lcov.info" });
// "Recording started"

get_diff_since_start

Compare current coverage against the recorded baseline. Input:

{
  lcovPath: string; // Required. Path to current LCOV file
}

Output:

{
  linesPercentageImpact: number,      // Positive = improvement, negative = regression
  branchesPercentageImpact: number    // Positive = improvement, negative = regression
}

Example:

get_diff_since_start({ lcovPath: "./coverage/lcov.info" });
// { linesPercentageImpact: +2.3, branchesPercentageImpact: +1.8 }

🔧 Technical Details

How It Works

1. Parses LCOV files using a production - grade parser that handles all LCOV format variations.
2. Calculates coverage percentages for overall project or individual files.
3. Stores baselines in a temporary directory for session - based tracking.
4. Returns compact JSON responses that consume minimal tokens.

LCOV Format Support

This server supports all standard LCOV file formats, including:

• Files with summary sections (SF:, end_of_record).
• Files with line - by - line data only (DA: entries).
• Files with branch coverage data (BRDA:, BRF:, BRH:).
• Mixed formats within the same file.

Troubleshooting

"LCOV file not found"

• Ensure you've run your test suite with coverage enabled first.
• Check that the path to your LCOV file is correct (relative paths are resolved from current working directory).
• Default path is ./coverage/lcov.info.

"No coverage data found for file"

• Verify the file path matches exactly as it appears in the LCOV file.
• Some test frameworks use absolute paths, others use relative paths.

"No baseline recording found"

• You must call start_recording before calling get_diff_since_start.
• Baselines are stored in temporary storage and cleared when the system restarts.

Development

# Install dependencies
npm install

# Build
npm run build

# Run tests (with coverage!)
npm test

# Run linter
npm run lint

# Test with MCP inspector
npm run inspect

📄 License

MIT © Yoni Goldberg

🔗 Links

• GitHub Repository
• npm Package
• MCP Documentation
• Report Issues

💡 Improvement ideas

• coverage_file_summary returns nested properties also declared as flat.
• Start recording overrides other sessions files.
• Improve record naming - setSessionBaseline, getDiffSinceBaseline.