Skip to main content
Glama
README.md
# Codecov MCP Server

A Codecov Model Context Protocol server in TypeScript.

- Tools for finding where your codebase is lacking tests.
- Prompts for suggesting which tests to write.

## Features

### Resources
- None yet

### Tools
- `get_commit_coverage_totals` - Returns the coverage totals for a given commit and the
coverage totals broken down by file. Uses [this api](https://docs.codecov.com/reference/repos_totals_retrieve).

### Prompts
- `suggest_tests` - Suggests tests to write based on Codecov report.

## Installation

Usage: Ask your AI agent to "run the get_commit_coverage_totals tool" in your chat.

Configure: No need to install anything, just run with `npx` and put in your Codecov API key from [here](https://app.codecov.io/account/) - Go to Settings -> Access.

And git url: `git remote get-url origin`

Cursor command: `npx -y codecov-mcp-server --api-key XXX --git-url XXX`
(On Windows) Cursor command: `cmd.exe /c npx -y codecov-mcp-server --api-key XXX --git-url XXX`

To use with Claude (or any AI), add the server config:

```json
{
  "mcpServers": {
    "codecov-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "codecov-mcp-server",
      ],
      "env": {
        "CODECOV_API_KEY": "XXX",
        "GIT_URL": "XXX"
      }
    }
  }
}
```

### Debugging

Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector), which is available as a package script:

```bash
npm run inspector
```

The Inspector will provide a URL to access debugging tools in your browser.

## Development

Install dependencies:
```bash
npm install
```

Build the server:
```bash
npm run build
```

For development with auto-rebuild:
```bash
npm run watch
```

TDQS

A3.6/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is clear and unambiguous.

Naming Consistency5/5

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.

Tool Count2/5

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.

Completeness2/5

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.

Maintenance

ActivityInactive
ResponsivenessNo issues