Codecov MCP server
io.github.egulatee/codecov·v1.1.0·6 starsMCP server for querying Codecov coverage data with configurable URL support
6 stars30 downloads/wk
Reviews
Write oneNobody has reviewed Codecov yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Codecov tools (3)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
get_commit_coverageGet coverage data for a specific commit, including overall coverage percentage and file-level changes.
get_file_coverageGet line-by-line coverage data for a specific file in a repository. Returns coverage percentages and line-level hit/miss information.
get_repo_coverageGet overall coverage statistics for a repository, optionally for a specific branch.
Public scan report
scanner v0.1.10 · 2026-10-01 · same rubric, same numbers if you re-run it
- Code scan17 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 223 days ago4/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Codecov compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 66/100
- higher than 23% of 48,255 servers
- Tools
- 3
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 6
- more than 85% of 28,688 servers
- Downloads a week
- 30
- more than 18% of 12,191 servers with a package
What its tools let an agent do: 3 read
Install Codecov in Claude Code, Cursor or VS Code
Runs npx -y mcp-server-codecov on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add codecov -- npx -y mcp-server-codecov
What the publisher says
From the Codecov repository's README, as published. We do not edit it. Read it on GitHub
MCP Server for Codecov
A Model Context Protocol (MCP) server that provides tools for querying Codecov coverage data. Supports both codecov.io and self-hosted Codecov instances with configurable URL endpoints.
📦 Published on npm: @egulatee/mcp-codecov 🐳 Docker image: ghcr.io/egulatee/mcp-server-codecov
📖 Learn More: Read about building this MCP server with AI in just 2 hours.
Quick Start (Claude Code)
Get started in under 2 minutes:
1. Get your Codecov API token
Create an API token (not an upload token) from your Codecov account:
- Go to codecov.io (or your self-hosted URL)
- Click your avatar → Settings → Access tab
- Click "Generate Token" and name it "MCP Server API Access"
- Copy the token value
2. Set your environment variable
Add to your shell profile (~/.zshrc or ~/.bashrc):
export CODECOV_TOKEN="your-api-token-here"Then reload: source ~/.zshrc
3. Install the MCP server
claude mcp add --transport stdio codecov \
--env CODECOV_BASE_URL=https://codecov.io \
--env CODECOV_TOKEN=${CODECOV_TOKEN} \
-- npx -y @egulatee/mcp-codecov4. Verify installation
claude mcp get codecovExpected output: codecov: @egulatee/mcp-codecov - ✓ Connected
That's it! You can now use Codecov tools in Claude Code. See Available Tools below.
Features
- File-level coverage: Get detailed line-by-line coverage data for specific files
- Commit coverage: Retrieve coverage statistics for individual commits
- Repository coverage: Get overall coverage metrics for repositories
- Pull request coverage: Analyze coverage changes and impact for pull requests
- Coverage comparison: Compare coverage between branches, commits, or tags
- Configurable URL: Point to any Codecov instance (codecov.io or self-hosted)
- Token authentication: API token support for accessing coverage data
Token Types
Important: Codecov has two different types of tokens:
- Upload Token: Used for pushing coverage reports TO Codecov during CI/CD. Found on your repository's Settings → General page.
- API Token: Used for reading coverage data FROM Codecov via the API. Created in your Codecov Settings → Access tab.
This MCP server requires an API token, not an upload token.
Available Tools
getfilecoverage
Get line-by-line coverage data for a specific file.
Parameters:
- owner (required): Repository owner (username or organization)
- repo (required): Repository name
- file_path (required): Path to the file within the repository (e.g., 'src/index.ts')
- ref (optional): Git reference (branch, tag, or commit SHA)
Example:
Get coverage for src/index.ts in owner/repo on main branchgetcommitcoverage
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Codecov: common questions
- Is Codecov MCP server safe?
- With care: it is graded C, so read the findings first (66/100). Read the Codecov safety report
- How do I install Codecov?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Codecov need an API key?
- Yes. The registry entry asks for
CODECOV_TOKEN. - Is Codecov maintained?
- The last commit was 257 days ago (2026-02-20). The latest release is v1.1.0.
- How does Codecov compare with other MCP servers?
- safety score 66/100 (higher than 23% of 48,255 servers); tools 3 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.