In-depth architectural comparison of the Dotnet Coverage MCP and Bumpguard MCP 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
Bumpguard MCP
Developer Tools · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Verdict Summary: Choose Dotnet Coverage MCP if you need specialized Developer Tools tools running via a local process. Choose Bumpguard MCP 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).
MCP server for .NET coverage: run tests, parse Cobertura, find uncovered branches, append tests.
Pre-flight dependency-upgrade impact analysis: reports exactly which of your code's API usages break before you bump a dependency, with line numbers, severity, and fix hints. Also verifies AI-written code against the actually-installed API to catch hallucinated calls. Static analysis only — never runs third-party code. Python + .NET. pip install bumpguard-mcp
Category & Scope
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 is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Bumpguard MCP belongs to Developer Tools using local stdio subprocess. Select Dotnet Coverage MCP when you need capabilities focused on developer tools and Bumpguard MCP when you require tools for developer tools.
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).
Bumpguard MCP Tools (5)
diff_versions
*"What changed between two versions of this library?"* The raw breaking‑change list, no code scan — good for planning a migration.
verify_snippet
*"Do the imports and API calls in this code really exist here?"* Catches hallucinated/typo'd package names (slopsquatting) and attributes that aren't on the installed package.
check_import
*"Is this package installed? If not, what's the closest real name?"*
list_symbols
*"What's the real public API of this package?"* Discover functions/classes/methods + signatures instead of guessing — for the installed version or any fetched version.