What is the key difference between Dotnet Coverage MCP and MCP Doctor?

Dotnet Coverage MCP belongs to the Developer Tools category with local stdio execution, while MCP Doctor belongs to the Developer Tools category with local stdio execution.

How do I install Dotnet Coverage MCP or MCP Doctor in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Dotnet Coverage MCP and MCP Doctor free or paid?

Dotnet Coverage MCP operates under a Free / Open Source model (No auth required). MCP Doctor operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Dotnet Coverage MCP lists 8 tools with 2 views and 1 GitHub stars. MCP Doctor lists 6 tools with 4 views and 1 GitHub stars.

Can I use both Dotnet Coverage MCP and MCP Doctor together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Dotnet Coverage MCP vs MCP Doctor

In-depth architectural comparison of the Dotnet Coverage MCP and MCP Doctor MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Dotnet Coverage MCP

Developer Tools · Local stdio

Quality: 47/100 (Fair) | Auth: No auth required

MCP Doctor

Developer Tools · Local stdio

Quality: 40/100 (Fair) | Auth: No auth required

Verdict Summary: Choose Dotnet Coverage MCP if you need specialized Developer Tools tools running via a local process. Choose MCP Doctor if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Dotnet Coverage MCP when:

You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: GetSourceFiles, RunTestsWithCoverage, GetCoverageSummary.

Explore Dotnet Coverage MCP Details

Choose MCP Doctor when:

You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: OPENAI_API_KEY, OPENAI_BASE_URL, MCP_DOCTOR_MODEL.
Primary tools included: Six-dimension MCP contract evaluation, Deterministic offline rule-based checks, Optional AI-enhanced review.

Feature & Specification Comparison

Specification	Dotnet Coverage MCP Developer Tools	MCP Doctor Developer Tools
Summary	MCP server for .NET coverage: run tests, parse Cobertura, find uncovered branches, append tests.	Check and improve the contract quality of any MCP server — for humans, agents, and platforms.
Category & Scope	Developer Tools	Developer Tools

Tools & Capabilities Breakdown

Dotnet Coverage MCP Tools (8)

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

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Dotnet Coverage MCP Configuration

mcpServers (Claude Desktop / Cursor)

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

MCP Doctor Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "mcp-doctor": {
      "command": "uvx",
      "args": [
        "mcp-doctor"
      ],
      "env": {
        "OPENAI_API_KEY": "YOUR_OPENAI_API_KEY_HERE",
        "OPENAI_BASE_URL": "YOUR_OPENAI_BASE_URL_HERE",
        "MCP_DOCTOR_MODEL": "YOUR_MCP_DOCTOR_MODEL_HERE"
      }
    }
  }
}

Frequently Asked Questions

Dotnet Coverage MCP is categorized under Developer Tools and uses a local stdio subprocess. In contrast, MCP Doctor belongs to Developer Tools using local stdio subprocess. Select Dotnet Coverage MCP when you need capabilities focused on developer tools and MCP Doctor when you require tools for developer tools.

More alternatives to Dotnet Coverage MCP More alternatives to MCP Doctor Developer Tools category hub