codecov-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GIT_URL | Yes | Git URL of the repository (e.g., from 'git remote get-url origin') | |
| CODECOV_API_KEY | Yes | Your Codecov API key from https://app.codecov.io/account/ |
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
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_commit_coverage_totalsA | Returns the Codecov coverage totals for a given commit and the coverage totals broken down by file |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| suggest_tests | Suggests tests to write based on Codecov report |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.