In-depth architectural comparison of the Figma Use and Dotnet Coverage 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
Figma Use
Developer Tools · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Dotnet Coverage Mcp
Developer Tools · Local stdio
Quality: 45/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Figma Use if you need specialized Developer Tools tools running via a local process. Choose Dotnet Coverage 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 Figma Use 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: FIGMA_USE_REMOTE_DEBUGGING_PORT.
Primary tools included: Imperative CLI commands for Figma object creation and styling, Declarative JSX rendering of Figma layouts and components, Support for 80+ design operations including auto-layout and variables.
Figma Use is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Dotnet Coverage Mcp belongs to Developer Tools using local stdio subprocess. Select Figma Use when you need capabilities focused on developer tools and Dotnet Coverage Mcp when you require tools for developer tools.
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).