Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Beschreibung vom Entwickler (englisches Original)
MCP server for .NET coverage: run tests, parse Cobertura, find uncovered branches, append tests.
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
COVERAGE_MCP_ALLOWED_ROOT, COVERAGE_MCP_DOTNET_TEST_TIMEOUT_MSWelche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Öffne Claude Desktop → Settings → Developer → Edit Config und füge dies in claude_desktop_config.json ein
{
"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"
}
}
}
}Führe das in deinem Terminal aus
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 --yesTrag die leeren Werte ein, bevor du ihn startest.
In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"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"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"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"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
Dieser Server läuft auf deinem Computer, und ChatGPT kann sich nur mit Servern im Internet verbinden. Wähle eine andere App.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
COVERAGE_MCP_ALLOWED_ROOT envCOVERAGE_MCP_DOTNET_TEST_TIMEOUT_MS envDiese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Läuft auf deinem Computer; die Tool-Liste erscheint nach der Installation in deiner KI-App.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 7. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto Hyeonu-Cha bestätigt, dem das Repo gehört
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieser Server läuft auf deinem Computer; es gibt keinen Endpunkt im Internet
Läuft auf deinem Computer und nutzt stattdessen lokale Einstellungen
Läuft auf deinem Computer; Tool-Listen können wir nur von Endpunkten im Internet lesen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.
Er läuft auf deinem Computer. Deine KI-App startet ihn bei Bedarf, und die Daten laufen nicht über die Server des Entwicklers (außer der Server ruft selbst einen Onlinedienst auf).
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.1.1) kam vor 6 Monaten in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Außerdem brauchst du .NET auf deinem Computer.
In derselben Kategorie: Spec Driven Development, Remote Desktop Commander, LexPact UK Contracts
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Generate UK-law contracts: NDA, service, freelance, recruiter terms of business, IR35.
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
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.
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:
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
| Tool | Description |
|---|---|
GetSourceFiles | Discover .cs files from a file, folder, or .csproj project. Returns file metadata (lines, method count) and smart batches grouped by lineBudget. |
RunTestsWithCoverage | Run 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. |
GetCoverageSummary | Parse 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. |
GetFileCoverage | Get 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. |
GetUncoveredBranches | Find uncovered branch conditions for methods matching a given name. Returns all matching methods with partial name support. Supports sessionId. |
GetCoverageDiff | Compare current Cobertura XML against baseline. Shows method-level changes including new and removed methods. Supports sessionId for concurrent isolation. |
AppendTestCode | Insert 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. |
CleanupSession | Remove session state files and TestResults/coveragereport directories. Pass sessionId to scope, or omit to clean artifacts older than maxAgeMinutes (default 120). |
For projects with many source files, the recommended workflow is:
GetSourceFiles on a folder or .csproj to get all files and smart batchesRunTestsWithCoverage with a broad filter (e.g., *) to collect coverage across all filesGetFileCoverage for each file in the current batch (instant XML parsing, no test re-run)GetUncoveredBranches for eachAppendTestCode to add test methodsGetCoverageDiff to verify improvementThis minimises dotnet test invocations (the main bottleneck) while still tracking per-file progress.
Multiple AI agents can run in parallel by passing a sessionId to each tool call, which isolates their coverage artifacts:
RunTestsWithCoverage creates TestResults-{hash}/ and coveragereport-{hash}/ per session, preventing one agent from deleting another's XML mid-parse.mcp-coverage/.coverage-state-{hash}, so ResolveCoberturaPath resolves to the correct XML for each sessionGetCoverageDiff stores baselines as .coverage-prev-{hash}.xml per sessionLimitation — build outputs are not session-scoped.
sessionIdisolates coverage *artifacts*, not the .NET *build*.dotnet testcompiles the target project into its sharedobj/andbin/, which are not per-session, so two agents runningRunTestsWithCoverageagainst the same test project at the same time collide on those outputs and fail withbuildError(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 theirdotnet testbuilds don't overlap.
Without sessionId, tools use shared defaults — safe for single-agent use.
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 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.
cd <path-to-dotnet-coverage-mcp>
dotnet restore
dotnet build
dotnet run
The server will start and wait for MCP messages over stdin/stdout.
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 mcp add coverage --env COVERAGE_MCP_ALLOWED_ROOT=/path/to/your/repo -- dotnet-coverage-mcp
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" } } } }
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" } } } }
Add to .vscode/mcp.json:
{
"servers": { "coverage": { "type": "stdio", "command": "dotnet-coverage-mcp", "env": { "COVERAGE_MCP_ALLOWED_ROOT": "/path/to/your/repo" } } } }
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" } } }
GetSourceFiles| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Path to a .cs file, folder, or .csproj project |
lineBudget | int | No | Max total lines per batch (default: 300). Small files are grouped together; large files get their own batch. |
RunTestsWithCoverage| Parameter | Type | Required | Description |
|---|---|---|---|
testProjectPath | string | Yes | Full path to the .csproj test project |
filter | string | Yes | Test filter string (matched against FullyQualifiedName). Use * or , for broad runs across multiple test classes. |
workingDir | string | No | Working directory; defaults to the project directory |
forceRestore | bool | No | When true, skips the --no-restore flag. Use after scaffolding a new test project or adding NuGet packages. |
sessionId | string | No | Isolates output directories (TestResults-{hash}/, coveragereport-{hash}/) and state files for concurrent multi-agent use. |
includeClass | string | No | Restrict 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. |
skipReport | bool | No | When 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| Parameter | Type | Required | Description |
|---|---|---|---|
summaryJsonPath | string | Yes | Full path to the generated Summary.json file |
belowTarget | double | No | When 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. |
topN | int | No | Return only the N lowest-branch-coverage classes (results are sorted worst-first). Omit for all classes. |
methodsPerClass | int | No | Keep at most this many lowest-branch-coverage methods per class, trimming the rest. Omit to keep all methods. |
GetFileCoverage| Parameter | Type | Required | Description |
|---|---|---|---|
coberturaXmlPath | string | Yes | Path to coverage.cobertura.xml (falls back to .mcp-coverage/.coverage-state if not found) |
sourceFileName | string | Yes | Source file name to look up (e.g., ExampleService.cs) |
sessionId | string | No | Resolves session-scoped state file for concurrent isolation. |
| targetRate | double | No | Coverage
Nur der Anfang wird gezeigt; den Rest findest du im Repo