codecov-mcp-server
Related Servers
Alternatives to codecov-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server that provides instant, token-efficient test coverage data for any programming language, allowing agents to query coverage summaries and track session progress.48 npm41MIT
- AlicenseAqualityAmaintenanceTest coverage intelligence MCP server for TypeScript and JavaScript projects. Analyzes coverage reports to find untested functions, computes cyclomatic complexity, and suggests test cases locally.438 npm3MIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server that gives AI assistants direct access to .NET test-coverage tooling, enabling them to run tests, parse Cobertura XML, identify uncovered branches, diff coverage between runs, and append test code.1MIT
- FlicenseAqualityDmaintenanceMCP server for Java branch coverage analysis using JaCoCo. Enables agent-style coverage feedback with per-test-class granularity and uncovered line identification.2-
- AlicenseNot gradedqualityBmaintenanceMCP server for testing assistance that scans codebases, identifies untested areas, generates and runs tests, and reports results.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceMCP server that performs mutation testing and diff scoping to score how trustworthy tests are for detecting regressions in changed code.MIT
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is clear and unambiguous.
The single tool name 'get_commit_coverage_totals' follows a clear verb_noun pattern and is descriptive. With only one tool, consistency is trivially satisfied, but the name itself is well-formed.
One tool is far too thin for a Codecov MCP server, which typically would need multiple operations (commits, branches, reports, etc.). The server appears to be scoped too narrowly.
The tool only provides commit coverage totals with file breakdown. Many obvious Codecov features are missing (e.g., coverage by branch, pull request, or trend analysis), creating significant gaps for most use cases.