Integration

Codecov integration

Codecov API for code coverage reporting and analysis. Track test coverage metrics across repositories, monitor coverage changes in pull requests, manage coverage uploads, and integrate with CI/CD pipelines. Provides detailed coverage reports, file-level analysis, comparisons, test results, and team collaboration features for maintaining high code quality standards.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Codecov.Built from the 35 Codecov tools below, on the connection you add once.

Common Codecov use cases

  • pre-merge coverage checks
  • coverage trend visualization
  • coverage diff analysis
  • CI/CD setup
  • user lookup
  • team management
  • security auditing
  • focused code review
  • flag-level PR review
  • PR coverage analysis

What you can do with Codecov

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Comparison, 6 operations

  • compare_commitsCompare commitsGETCompares coverage between two commits or for a pull request showing base/head totals and patch coverage.
  • compare_componentsCompare componentsGETCompares coverage at the component level between two commits or for a pull request.
  • compare_fileCompare fileGETCompares coverage for a specific file between two commits or for a pull request with line-by-line diff.
  • compare_flagsCompare flagsGETCompares coverage at the flag level between two commits or for a pull request.
  • compare_impacted_filesCompare impacted filesGETReturns the list of files impacted by coverage changes between two commits or for a pull request.
  • compare_segmentsCompare segmentsGETReturns segmented file comparison showing only the impacted segments of a file for efficient review.

Repository, 3 operations

  • get_repositoryGet repositoryGETRetrieves coverage information for a repository including overall coverage percentage, line counts, and repository metadata.
  • get_repository_configGet repository configGETRetrieves repository configuration including upload token and graph token.
  • list_repositoriesList repositoriesGETReturns a paginated list of repositories for the specified owner with optional filtering.

User, 3 operations

  • get_userGet userGETRetrieves details for a specific user within an organization.
  • list_usersList usersGETLists users belonging to the specified owner organization.
  • update_userUpdate userPATCHUpdates a user's activation status to activate or deactivate their access.

Branch, 2 operations

  • get_branchGet branchGETRetrieves detailed coverage data for a specific branch including head commit and coverage totals.
  • list_branchesList branchesGETLists branches with their coverage data including coverage percentage and head commit information.

Commit, 2 operations

  • get_commitGet commitGETRetrieves detailed coverage data for a specific commit including file-level breakdown and comparison with parent commit.
  • list_commitsList commitsGETLists commits with coverage data for a repository. Returns commit SHA, coverage metrics, and CI information.

Evaluation, 2 operations

  • compare_evalsCompare evalsGETReturns a comparison of evaluations between two commits for a repository.
  • get_eval_summaryGet eval summaryGETReturns a summary of evaluations for a specific commit in a repository with optional classname filtering.

Flag, 2 operations

  • get_flag_coverage_trendGet flag coverage trendGETRetrieves coverage trend data over time for a specific flag showing historical flag-level coverage metrics.
  • list_flagsList flagsGETLists coverage flags for a repository allowing coverage segmentation by test type, environment, or component.

Owner, 2 operations

  • get_ownerGet ownerGETReturns details for a specific owner including service, username, and display name.
  • list_ownersList ownersGETReturns a paginated list of owners (organizations/users) accessible to the authenticated user.

Pull, 2 operations

  • get_pullGet pullGETRetrieves detailed coverage data for a pull request including base/head coverage totals and CI status.
  • list_pullsList pullsGETLists pull requests with coverage data showing coverage change and comparison metrics against the base branch.

Report, 2 operations

  • get_coverage_reportGet coverage reportGETRetrieves the full coverage report for a repository commit with line-by-line coverage data for all files.
  • get_coverage_report_treeGet coverage report treeGETRetrieves the coverage report as a tree structure organized by directory hierarchy with configurable depth.

Test result, 2 operations

  • get_test_resultGet test resultGETRetrieves detailed information for a specific test result by its ID.
  • list_test_resultsList test resultsGETLists test results for a repository with filtering by branch, commit, outcome, and duration range.

Component, 1 operation

  • list_componentsList componentsGETLists coverage components that group files by path patterns for organized coverage tracking across different parts of the codebase.

File, 1 operation

  • get_file_coverageGet file coverageGETRetrieves line-by-line coverage data for a specific file showing which lines are covered, missed, or partial.

Session, 1 operation

  • list_user_sessionsList user sessionsGETReturns a paginated list of users' login sessions for the specified organization. Requires admin access.

Test analytics, 1 operation

  • list_test_analyticsList test analyticsGETLists test analytics for a repository showing test run details including name, classname, outcome, and duration.

Totals, 1 operation

  • get_coverage_totalsGet coverage totalsGETRetrieves coverage totals for a commit broken down by file with optional filtering by path, flag, or component.

Trend, 1 operation

  • get_coverage_trendGet coverage trendGETRetrieves coverage trend data over time showing daily, weekly, or monthly coverage percentages for historical analysis.

Upload, 1 operation

  • list_commit_uploadsList commit uploadsGETLists coverage uploads for a specific commit showing CI provider, job info, and upload flags.

Use Codecov from Claude Code, Cursor or Codex

Connect Codecov in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Codecov operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Codecov

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Codecov once

    Add your Codecov connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Codecov integration FAQ

What can you do with the Codecov integration?

LiveContext exposes 35 operations on Codecov, covering comparison, repository, user and branch. Common uses include pre-merge coverage checks, coverage trend visualization and coverage diff analysis.

Popular integrations

Browse the whole catalog