Dotnet Coverage Mcp
Run .NET tests with coverage from your agent, parse Cobertura, surface uncovered branches, and extend test files without manual report spelunking.
Overview
dotnet-coverage-mcp is a MCP server for the Ship phase that runs .NET tests, parses Cobertura coverage, finds gaps, and appends tests.
What is this MCP server?
- Run dotnet test and parse Cobertura coverage reports via MCP (NuGet dotnet-coverage-mcp v0.1.1)
- Find uncovered branches to prioritize the next test you write
- Append generated tests into existing test projects from agent workflows
- Optional COVERAGE_MCP_ALLOWED_ROOT filesystem sandbox; default dotnet test timeout 600000 ms (10 minutes)
- Default dotnet test timeout 600000 ms (10 minutes) via COVERAGE_MCP_DOTNET_TEST_TIMEOUT_MS
- Version 0.1.1; optional COVERAGE_MCP_ALLOWED_ROOT restricts all tool filesystem access
What problem does it solve?
Your agent cannot see which branches lack tests after dotnet test, so coverage work stalls on manual Cobertura reading.
Who is it for?
.NET indie hackers and small teams who want agent-assisted coverage loops before shipping API or service changes.
Skip if: Pure frontend or non-.NET repos, or teams that forbid automated test file writes without human review gates.
What do I get? / Deliverables
After install, your agent can run covered test cycles, list uncovered branches, and propose appended tests aligned to real gaps.
- Parsed coverage summaries and uncovered branch lists from Cobertura
- Appended test code targeting identified gaps in existing test projects
Recommended MCP Servers
Journey fit
Coverage-driven test iteration belongs in Ship because you close quality gaps before release, not while sketching features. Testing is the right shelf for MCP tools that execute dotnet test, read Cobertura output, and drive targeted test additions.
How it compares
.NET coverage and test-append MCP, not a generic code-review skill or a security scanner.
Common Questions / FAQ
Who is dotnet-coverage-mcp for?
Solo builders and small teams on .NET who use MCP agents to improve test coverage with Cobertura-backed feedback.
When should I use dotnet-coverage-mcp?
Use it in Ship/testing when you are closing release blockers and need uncovered branch lists plus guided test additions after dotnet test.
How do I add dotnet-coverage-mcp to my agent?
Add the NuGet dotnet-coverage-mcp stdio server to your MCP config, ensure dotnet SDK and test projects are on PATH, and set COVERAGE_MCP_ALLOWED_ROOT in shared environments.