Skip to main content
Glama
egulatee

Codecov MCP Server

by egulatee

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CODECOV_TOKENYesCodecov API token (not upload token). Required for authentication.
CODECOV_BASE_URLNoBase URL of the Codecov instance (must use https). For self-hosted instances, e.g., https://codecov.your-company.com.https://codecov.io

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}
prompts
{
  "listChanged": true
}
resources
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_file_coverageB

Get line-by-line coverage data for a specific file in a repository. Returns coverage percentages and line-level hit/miss information.

get_commit_coverageA

Get coverage data for a specific commit, including overall coverage percentage and file-level changes.

get_repo_coverageA

Get overall coverage statistics for a repository, optionally for a specific branch.

get_pull_request_coverageA

Get coverage data for a specific pull request, including coverage changes and file-level impact.

compare_coverageA

Compare coverage between two git references (branches, commits, or tags).

Prompts

Interactive templates invoked by user choice

NameDescription
analyze_coverageGet comprehensive coverage analysis for a repository
compare_commitsCompare coverage changes between two commits
find_low_coverageIdentify files with coverage below a threshold

Resources

Contextual data attached and managed by the client

NameDescription
Getting Started GuideQuick start guide for using the Codecov MCP server
GitHub Actions IntegrationExample GitHub Actions workflow for Codecov
Common Query PatternsExamples of common Codecov queries
Configuration GuideHow to configure CODECOV_BASE_URL and CODECOV_TOKEN

TDQS

A3.9/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a distinct coverage aspect: repo, commit, file, pull request, or comparison between references. No functional overlap.

Naming Consistency5/5

All tools follow a clear verb_noun pattern (get_<entity>_coverage, compare_coverage), with no mixing of styles.

Tool Count5/5

Five tools cover the essential coverage operations for a code coverage server, neither too few nor excessive.

Completeness4/5

Covers repo, commit, file, PR, and comparison coverage queries. Minor gap: no tool for listing commits or historical trends, but core use cases are well supported.

Maintenance

ActivityInactive
ResponsivenessNo issues