testing / Node.js and MCP
test-intel-mcp
Turn coverage reports and source layout into practical test-priority signals.
test-intel-mcp reads common JavaScript and TypeScript coverage formats, maps source files to their likely tests, and adds heuristic complexity signals. It is designed to help an MCP client decide where testing effort is most useful next.
verified open-source case study
A 98.42 percent covered project still contains two uncovered lines.
The published report command inspected a real lcov artifact produced by all 22 upstream tests from p-limit 7.3.1 at commit df47604.
observed output
tests 22 passedline 98.42 percentuncovered 13, 14branch 12:3:0
what it exposes
Capabilities
- Parse lcov, Istanbul JSON, and Cobertura coverage reports
- Surface uncovered files, functions, lines, and branches from coverage data
- Map source files to corresponding or importing test files
- Estimate function complexity and suggest categories of test cases
workflow integration
Keep the evidence in the run
Turn an existing coverage artifact into a workflow summary.
- uses: barissozudogru/test-intel-mcp@v0.8.1good fit
Use it when
- Triaging coverage gaps in TypeScript and JavaScript projects
- Giving an MCP client local test context without an external service
- Prioritizing complex functions for human review and stronger tests
operating limits
Know before using
- Source-to-test matching does not prove that every function is behaviorally tested
- Complexity and test suggestions are heuristic signals, not semantic guarantees
- Use native coverage data as the source of truth when it is available