Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Dotnet Coverage MCP

by Hyeonu-Chaversion 0.1.1i★ –iRuns on your computer
Registry nameio.github.Hyeonu-Cha/dotnet-coverage-mcp

Install

Overview

Description from the maker (original English)

MCP server for .NET coverage: run tests, parse Cobertura, find uncovered branches, append tests.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: COVERAGE_MCP_ALLOWED_ROOT, COVERAGE_MCP_DOTNET_TEST_TIMEOUT_MS

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "dotnet-coverage": {
      "command": "dnx",
      "args": [
        "dotnet-coverage-mcp",
        "--yes"
      ],
      "env": {
        "COVERAGE_MCP_ALLOWED_ROOT": "your-value",
        "COVERAGE_MCP_DOTNET_TEST_TIMEOUT_MS": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add dotnet-coverage --env COVERAGE_MCP_ALLOWED_ROOT=your-value --env COVERAGE_MCP_DOTNET_TEST_TIMEOUT_MS=your-value -- dnx dotnet-coverage-mcp --yes

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "dotnet-coverage": {
      "command": "dnx",
      "args": [
        "dotnet-coverage-mcp",
        "--yes"
      ],
      "env": {
        "COVERAGE_MCP_ALLOWED_ROOT": "your-value",
        "COVERAGE_MCP_DOTNET_TEST_TIMEOUT_MS": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "dotnet-coverage": {
      "type": "stdio",
      "command": "dnx",
      "args": [
        "dotnet-coverage-mcp",
        "--yes"
      ],
      "env": {
        "COVERAGE_MCP_ALLOWED_ROOT": "your-value",
        "COVERAGE_MCP_DOTNET_TEST_TIMEOUT_MS": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • COVERAGE_MCP_ALLOWED_ROOT env
    Restrict every tool's filesystem access to this subtree. Recommended for shared environments. When unset, the server logs a warning and accepts any path.
  • COVERAGE_MCP_DOTNET_TEST_TIMEOUT_MS env
    Override the dotnet test timeout in milliseconds. Default: 600000 (10 minutes).

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account Hyeonu-Cha, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 18349 servers in this category
  • Published to the registry more recently than 7% of the other 18349 servers in this category
  • Basic checks equal to or better than 100% of the other 18349 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Dotnet Coverage MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 6 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need .NET on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, arr-mcp

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago
Install

arr-mcp

by bardesss

One server, 40 tools, the whole media stack: *arrs, Jellyfin, Plex, Seerr, Cleanuparr, downloaders

Runs on your computerUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

dotnet-coverage-mcp

An MCP (Model Context Protocol) server that gives AI assistants — Claude Code, Gemini CLI, and others — direct access to .NET test-coverage tooling. Run dotnet test, parse Cobertura XML, identify uncovered branches, diff coverage between runs, and append test code — all over stdio.

Purpose

This server lets an AI assistant run unit tests, collect coverage data, and analyse results — all without leaving the chat. Instead of manually running dotnet test and parsing reports, the AI can call the server's tools directly to:

  • Discover source files and build smart batches by line budget
  • Run a filtered set of tests and collect coverage
  • Read compact, AI-optimised coverage summaries (method-level line/branch rates)
  • Check per-file coverage against a configurable target rate (default 80%)
  • Identify uncovered branches as structured JSON
  • Diff coverage between runs to see only what changed
  • Append new test code to an existing test file with atomic writes

How It Works

The server starts as a console process and communicates over stdio using the MCP protocol. An MCP-compatible client (Claude Code, Gemini CLI, etc.) launches the process and calls its tools as if they were functions.

AI Client  <--stdio/MCP-->  dotnet-coverage-mcp  <--shell-->  dotnet test + reportgenerator

Available Tools

ToolDescription
GetSourceFilesDiscover .cs files from a file, folder, or .csproj project. Returns file metadata (lines, method count) and smart batches grouped by lineBudget.
RunTestsWithCoverageRun dotnet test with XPlat Code Coverage, generate a JSON summary via reportgenerator. Returns paths to Summary.json and coverage.cobertura.xml. Supports forceRestore and sessionId for concurrent isolation.
GetCoverageSummaryParse Summary.json into structured class/method coverage data sorted worst-first by branch coverage. Optional belowTarget/topN/methodsPerClass filters trim the response to what still needs work.
GetFileCoverageGet coverage for a single source file from Cobertura XML. Returns allMeetTarget (true when all classes meet the configured targetRate for both line and branch coverage; default 0.8). Supports sessionId.
GetUncoveredBranchesFind uncovered branch conditions for methods matching a given name. Returns all matching methods with partial name support. Supports sessionId.
GetCoverageDiffCompare current Cobertura XML against baseline. Shows method-level changes including new and removed methods. Supports sessionId for concurrent isolation.
AppendTestCodeInsert or append C# test code into a test file. Supports anchor-based insertion with whitespace-tolerant fallback matching. Uses atomic writes to prevent file corruption.
CleanupSessionRemove session state files and TestResults/coveragereport directories. Pass sessionId to scope, or omit to clean artifacts older than maxAgeMinutes (default 120).

Batch Workflow

For projects with many source files, the recommended workflow is:

  1. Discover — Call GetSourceFiles on a folder or .csproj to get all files and smart batches
  2. Run once — Call RunTestsWithCoverage with a broad filter (e.g., *) to collect coverage across all files
  3. Check per-file — Call GetFileCoverage for each file in the current batch (instant XML parsing, no test re-run)
  4. Focus — Pick the 3 lowest branch-coverage methods and call GetUncoveredBranches for each
  5. Write tests — Use AppendTestCode to add test methods
  6. Re-run and diff — Run tests once, call GetCoverageDiff to verify improvement
  7. Repeat — Continue until batch files meet the target rate (default 80%) or 3 cycles with no improvement, then move to next batch

This minimises dotnet test invocations (the main bottleneck) while still tracking per-file progress.

Concurrency

Multiple AI agents can run in parallel by passing a sessionId to each tool call, which isolates their coverage artifacts:

  • Isolated output directories — RunTestsWithCoverage creates TestResults-{hash}/ and coveragereport-{hash}/ per session, preventing one agent from deleting another's XML mid-parse
  • Scoped state files — Coverage state is written to .mcp-coverage/.coverage-state-{hash}, so ResolveCoberturaPath resolves to the correct XML for each session
  • Scoped baselines — GetCoverageDiff stores baselines as .coverage-prev-{hash}.xml per session
  • Atomic writes — All file writes (state files and test code) use write-to-temp-then-rename to prevent corruption from race conditions or process crashes

Limitation — build outputs are not session-scoped. sessionId isolates coverage *artifacts*, not the .NET *build*. dotnet test compiles the target project into its shared obj/ and bin/, which are not per-session, so two agents running RunTestsWithCoverage against the same test project at the same time collide on those outputs and fail with buildError (e.g. CS2012: the file is being used by another process). Run parallel agents against different test projects, or on separate working copies of the repo. Multiple agents on one project are fine as long as their dotnet test builds don't overlap.

Without sessionId, tools use shared defaults — safe for single-agent use.

Requirements

  • .NET 9.0 SDK (or later) — https://dotnet.microsoft.com/download
  • reportgenerator global tool — the server shells out to it to render coverage reports (installed in the Install step below)
  • An MCP-compatible client (Claude Code, Gemini CLI, etc.)
  • `COVERAGE_MCP_ALLOWED_ROOT` — recommended. Set to your repository root to restrict every tool's filesystem access to that subtree. Any path passed by the client outside this root is rejected with pathNotAllowed. When unset, the server logs a warning once and accepts any path (backward-compatible, but not recommended for shared environments).
  export COVERAGE_MCP_ALLOWED_ROOT=/path/to/your/repo

Install

Install the server as a global .NET tool from NuGet:

dotnet tool install --global dotnet-coverage-mcp

The server depends on the reportgenerator global tool to render coverage reports — install it too:

dotnet tool install --global dotnet-reportgenerator-globaltool

After install, the dotnet-coverage-mcp command is on your PATH.

Build & Run (from source)

cd <path-to-dotnet-coverage-mcp>

Restore dependencies

dotnet restore

Build

dotnet build

Run

dotnet run

The server will start and wait for MCP messages over stdin/stdout.

MCP Client Configuration

After installing the global tool (dotnet tool install --global dotnet-coverage-mcp), register the server with your MCP client. Set COVERAGE_MCP_ALLOWED_ROOT to the repository you want the server to operate on.

Claude Code
claude mcp add coverage --env COVERAGE_MCP_ALLOWED_ROOT=/path/to/your/repo -- dotnet-coverage-mcp
Claude Desktop

Add to claude_desktop_config.json (Settings → Developer → Edit Config):

{

"mcpServers": { "coverage": { "command": "dotnet-coverage-mcp", "env": { "COVERAGE_MCP_ALLOWED_ROOT": "/path/to/your/repo" } } } }

Cursor

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per-project):

{

"mcpServers": { "coverage": { "command": "dotnet-coverage-mcp", "env": { "COVERAGE_MCP_ALLOWED_ROOT": "/path/to/your/repo" } } } }

VS Code (GitHub Copilot)

Add to .vscode/mcp.json:

{

"servers": { "coverage": { "type": "stdio", "command": "dotnet-coverage-mcp", "env": { "COVERAGE_MCP_ALLOWED_ROOT": "/path/to/your/repo" } } } }

Run from source

To run from source instead of the global tool, use dotnet run:

{

"mcpServers": { "coverage": { "command": "dotnet", "args": ["run", "--project", " "], "transport": "stdio" } } }

Or point directly at the compiled executable:

{

"mcpServers": { "coverage": { "command": " \\bin\\Debug\\net9.0\\DotNetCoverageMcp.exe", "transport": "stdio" } } }

Tool Parameters

GetSourceFiles
ParameterTypeRequiredDescription
pathstringYesPath to a .cs file, folder, or .csproj project
lineBudgetintNoMax total lines per batch (default: 300). Small files are grouped together; large files get their own batch.
RunTestsWithCoverage
ParameterTypeRequiredDescription
testProjectPathstringYesFull path to the .csproj test project
filterstringYesTest filter string (matched against FullyQualifiedName). Use * or , for broad runs across multiple test classes.
workingDirstringNoWorking directory; defaults to the project directory
forceRestoreboolNoWhen true, skips the --no-restore flag. Use after scaffolding a new test project or adding NuGet packages.
sessionIdstringNoIsolates output directories (TestResults-{hash}/, coveragereport-{hash}/) and state files for concurrent multi-agent use.
includeClassstringNoRestrict coverage collection to types matching this name (coverlet Include filter, applied via a generated runsettings file passed with --settings). Independent of filter — pass an explicit value to scope coverage; omit it to collect coverage for everything the run touches. Namespace-qualified names are not supported.
skipReportboolNoWhen true, skips the reportgenerator JSON-summary step and returns only the Cobertura XML path. Faster for the inner test loop, where GetFileCoverage/GetUncoveredBranches/GetCoverageDiff read the XML directly. Leave false (default) when you need GetCoverageSummary's Summary.json.
GetCoverageSummary
ParameterTypeRequiredDescription
summaryJsonPathstringYesFull path to the generated Summary.json file
belowTargetdoubleNoWhen set (a fraction in [0,1], e.g. 0.8), return only classes whose line OR branch coverage is below this threshold. Omit for all classes.
topNintNoReturn only the N lowest-branch-coverage classes (results are sorted worst-first). Omit for all classes.
methodsPerClassintNoKeep at most this many lowest-branch-coverage methods per class, trimming the rest. Omit to keep all methods.
GetFileCoverage
ParameterTypeRequiredDescription
coberturaXmlPathstringYesPath to coverage.cobertura.xml (falls back to .mcp-coverage/.coverage-state if not found)
sourceFileNamestringYesSource file name to look up (e.g., ExampleService.cs)
sessionIdstringNoResolves session-scoped state file for concurrent isolation.

| targetRate | double | No | Coverage

Only the beginning is shown; read the rest in the repo

Ask PopNx