Codecov MCP by usefulapi

Most tools target a clearly distinct resource+action, but the coverage-report family (get_coverage_report, get_coverage_totals, get_report_tree) all serve a commit and could be confused at a glance; only the descriptions' output-shape details distinguish them. Compare vs compare_impacted_files and get_pull vs list_pulls are similarly close but adequately separated.

Every tool uses the same codecov_ prefix followed by a consistent verb_noun snake_case pattern (get_repo, list_commits, compare_impacted_files). No mixed conventions or vague verb styles.

24 tools is on the heavy side, but each maps to a distinct Codecov REST endpoint across repos, branches, commits, pulls, flags, components, and test results. The count is justified by the breadth of the read-only domain, though it sits at the upper edge of comfortable.

The read-only surface is broad: owners, users, repos, config, branches, commits, uploads, pulls, coverage reports/totals/trends, flags, components, and test results are all covered. Minor gaps exist (no single-flag/component/test-result detail or search endpoint), but core coverage workflows are complete.