# Reported issues for codecov

Pod holds 17 of 54 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to [codecov](/mcp/codecov).

## Most discussed

### Add MCP prompts and resources for LobeHub marketplace discovery

## Problem

LobeHub marketplace listing currently shows:
- ❌ 0 Tools (should show 3)
- ❌ 0 Prompts
- ❌ 0 Resources
- ⚠️ "Unvalidated" status

**Root Cause**: Missing `mcpName` field in package.json prevents proper tool discovery by LobeHub indexer.

## Solution

Implement complete MCP server capabilities for proper LobeHub discovery:

1. **Fix package.json metadata** - Add `mcpName` field for LobeHub indexing
2. **Add prompts capability** - 3 useful prompt templates for common Codecov queries
3.

[Read the thread](https://github.com/egulatee/mcp-server-codecov/issues/52) · 2025-12-21 · closed · 1 comment

### Code quality improvements: typed interfaces, data-driven patterns, and test refactoring

## Description

Several targeted, non-breaking code quality improvements identified during codebase review. All changes improve legibility, type safety, testability, and maintainability.

## Changes

### 1. Typed API response interfaces (`src/types.ts`, `src/client.ts`)
- Replace pervasive `any` types with proper typed interfaces (`FileCoverageResponse`, `CommitCoverageResponse`, `RepoCoverageResponse`, `PullRequestCoverageResponse`, `CompareCoverageResponse`, `CoverageTotal`)
- `LRUCache<any>` 

[Read the thread](https://github.com/egulatee/mcp-server-codecov/issues/116) · 2026-02-20 · closed · 0 comments

### feat: publish static tool manifest (tools.json) as a versioned build artifact

## Context

[openclaw-operator#23](https://github.com/realestateanalyzorinfra/openclaw-operator/issues/23) describes a bug where the `mcp-bridge` plugin registers codecov tools via an `async` export. OpenClaw's plugin host does not `await` the returned Promise, so any `api.registerTool()` calls that happen after the `tools/list` response arrives may be silently dropped.

The recommended fix (Option A in that issue) is to register tools **synchronously** using a statically-known list and defer th

[Read the thread](https://github.com/egulatee/mcp-server-codecov/issues/114) · 2026-02-17 · closed · 0 comments

### Ensure socat is installed for stdio-to-socket MCP bridging

## Summary

`socat` is a common requirement for connecting MCP clients to servers running inside Docker containers via stdio-to-TCP bridging. Currently there is no documentation or setup ensuring `socat` is available in the environment or image.

## Problem

When running the server in Docker, MCP clients (e.g. Claude Desktop, Cursor) communicate over stdio. To bridge this to a TCP socket inside a container, users typically need `socat`:

```bash
socat TCP:localhost:3000 STDIO
```

Without `socat

[Read the thread](https://github.com/egulatee/mcp-server-codecov/issues/112) · 2026-02-17 · closed · 0 comments

### feat: publish multi-platform Docker image to ghcr.io

## Summary

Publish a public, multi-platform Docker image to GitHub Container Registry (`ghcr.io`) so users can run the MCP server without installing Node.js or the npm package directly.

**Image:** `ghcr.io/egulatee/mcp-server-codecov`

---

## Motivation

Currently the only installation paths are:
- `npm install -g @egulatee/mcp-codecov`
- `npx -y @egulatee/mcp-codecov`

A Docker image adds a zero-dependency distribution path, improves reproducibility, and enables container-native workflows (C

[Read the thread](https://github.com/egulatee/mcp-server-codecov/issues/110) · 2026-02-17 · closed · 0 comments

### Optimize LLM Context Footprint: Reduce Token Usage by 38-65%

## Problem Summary

The Codecov MCP server currently has inefficiencies that increase LLM context window usage unnecessarily:

1. **JSON Pretty-Printing Overhead**: All 5 tool responses use `JSON.stringify(result, null, 2)`, adding 33-50% token overhead
2. **No Caching**: Every tool call makes fresh API requests, missing reuse opportunities
3. **Embedded Documentation**: 120+ lines of hardcoded strings that could be externalized
4. **Code Duplication**: 5 identical response wrapper patterns acro

[Read the thread](https://github.com/egulatee/mcp-server-codecov/issues/108) · 2026-02-16 · closed · 0 comments

### Rename npm package from mcp-server-codecov to @egulatee/mcp-codecov

## Description
Change the npmjs publication name from `mcp-server-codecov` to the scoped package `@egulatee/mcp-codecov` to follow modern npm conventions and match other MCP server naming patterns.

## Changes Required
- Update package.json name field: `mcp-server-codecov` → `@egulatee/mcp-codecov`
- Update binary name: `mcp-server-codecov` → `mcp-codecov`
- Update mcpName: `io.github.egulatee/codecov` → `@egulatee/codecov`
- Update all documentation files (README.md, CHANGELOG.md, RELEASE.md, P

[Read the thread](https://github.com/egulatee/mcp-server-codecov/issues/106) · 2026-02-13 · closed · 0 comments

### Add flags and components tools (API-verified endpoints)

## Summary

Add MCP tools for querying coverage flags and components using verified CodeCov v2 API endpoints. These are advanced features for organizations using CodeCov's flag and component systems.

## Verified API Endpoints

Based on official CodeCov v2 API documentation:

### 1. Flags List
- **Endpoint**: `GET /api/v2/gh/{owner}/repos/{repo}/flags`
- **Category**: Flags
- **Status**: ✅ Verified in official API docs

### 2. Components List
- **Endpoint**: `GET /api/v2/gh/{owner}/repos/{repo}/

[Read the thread](https://github.com/egulatee/mcp-server-codecov/issues/103) · 2026-02-12 · open · 0 comments

## Most recent

### Add advanced coverage report tools (API-verified endpoints)

## Summary

Add MCP tools for advanced coverage reports using verified CodeCov v2 API endpoints. These provide alternative views and more detailed coverage data.

## Verified API Endpoints

Based on official CodeCov v2 API documentation:

### 1. Commit Coverage Report
- **Endpoint**: `GET /api/v2/gh/{owner}/repos/{repo}/commits/{commit}/report/`
- **Category**: Coverage
- **Status**: ✅ Verified in official API docs
- **Note**: Different from commit detail endpoint - provides more detailed covera

[Read the thread](https://github.com/egulatee/mcp-server-codecov/issues/102) · 2026-02-12 · open · 0 comments

### Add repository configuration tool (read-only, API-verified endpoint)

## Summary

Add MCP tool for viewing repository configuration using verified CodeCov v2 API endpoint. **Note**: This is read-only - the API does not support updating configuration.

## Verified API Endpoint

Based on official CodeCov v2 API documentation:

### Repository Config
- **Endpoint**: `GET /api/v2/gh/{owner}/repos/{repo}/config`
- **Category**: Repos
- **Status**: ✅ Verified in official API docs
- **Capabilities**: READ-ONLY (no PATCH/PUT endpoints exist)

## Proposed Tool

### `get_rep

[Read the thread](https://github.com/egulatee/mcp-server-codecov/issues/101) · 2026-02-12 · open · 0 comments

### Add coverage trend/history tool (API-verified endpoint)

## Summary

Add MCP tool for retrieving historical coverage data and trends using verified CodeCov v2 API endpoints.

## Verified API Endpoint

Based on official CodeCov v2 API documentation:

### Coverage Trend
- **Endpoint**: `GET /api/v2/gh/{owner}/repos/{repo}/coverage/`
- **Category**: Coverage
- **Status**: ✅ Verified in official API docs
- **Description**: Retrieves historical coverage metrics over time

## Proposed Tool

### `get_coverage_history`

Get coverage trend data over time.

```

[Read the thread](https://github.com/egulatee/mcp-server-codecov/issues/100) · 2026-02-12 · open · 0 comments

### Add branch listing and detail tools (API-verified endpoints)

## Summary

Add MCP tools for listing and querying branch-specific coverage data using verified CodeCov v2 API endpoints.

## Verified API Endpoints

Based on official CodeCov v2 API documentation:

### 1. Branch List
- **Endpoint**: `GET /api/v2/gh/{owner}/repos/{repo}/branches`
- **Category**: Branches
- **Status**: ✅ Verified in official API docs

### 2. Branch Detail
- **Endpoint**: `GET /api/v2/gh/{owner}/repos/{repo}/branches/{branch}`
- **Category**: Branches  
- **Status**: ✅ Verified in

[Read the thread](https://github.com/egulatee/mcp-server-codecov/issues/99) · 2026-02-12 · open · 0 comments

### Add pull request coverage tools (API-verified endpoints)

## Summary

Add MCP tools for pull request coverage analysis using verified CodeCov v2 API endpoints. This enables PR-based coverage workflows and quality gates.

## Verified API Endpoints

Based on official CodeCov v2 API documentation:

### 1. Pull Request Detail
- **Endpoint**: `GET /api/v2/gh/{owner}/repos/{repo}/pulls/{pull_number}`
- **Category**: Pulls
- **Status**: ✅ Verified in official API docs

### 2. Coverage Comparison  
- **Endpoint**: `GET /api/v2/gh/{owner}/repos/{repo}/compare/{

[Read the thread](https://github.com/egulatee/mcp-server-codecov/issues/98) · 2026-02-12 · closed · 0 comments

### Remove activate_repository tool - endpoint does not exist in CodeCov API

## Problem

The `activate_repository` tool was added in PR #94 (v1.2.0) based on the assumption that a `POST /api/v2/gh/{owner}/repos/{repo}/activate` endpoint exists in the CodeCov v2 API. However, after thorough analysis of the official CodeCov API documentation, **this endpoint does not exist**.

## Evidence

1. **Not in official API documentation** - The CodeCov v2 API reference lists no `/activate` endpoint
2. **404 errors on docs** - Attempting to access documentation for this endpoint ret

[Read the thread](https://github.com/egulatee/mcp-server-codecov/issues/97) · 2026-02-12 · closed · 0 comments

### Publish version 1.2.0 to npm

## Root Cause

Version 1.2.0 was manually set in `package.json`, but the **Version Bump workflow was never run**, so:
- ❌ No `v1.2.0` git tag was created
- ❌ Release workflow was never triggered  
- ❌ Package was never published to npm

## Current Status

- **package.json version**: 1.2.0 ✅
- **Latest git tag**: v1.1.0 ❌ (v1.2.0 doesn't exist)
- **npm registry version**: 1.1.0 ❌

## How to Fix

### Option 1: Use the Version Bump Workflow (Recommended)

If PR #94 has **NOT** been merged to main y

[Read the thread](https://github.com/egulatee/mcp-server-codecov/issues/96) · 2026-02-12 · closed · 0 comments

### Add CI testing for newer Node.js versions (24.x, 25.x)

## Summary

The project currently tests on Node.js 20.x and 22.x in CI. We should add testing for newer Node.js versions to ensure compatibility and future-proof the codebase.

## Current State

**Testing (CI):**
- ✅ Node.js 20.x (LTS - Active until 2026-04-30)
- ✅ Node.js 22.x (LTS - Active until 2027-04-30)

**Engine requirement (`package.json`):**
```json
"engines": {
  "node": ">=20.0.0"
}
```

## Proposed Changes

Add the following Node.js versions to the CI test matrix:

- **Node.js 24.x**

[Read the thread](https://github.com/egulatee/mcp-server-codecov/issues/95) · 2026-02-12 · open · 0 comments

### Add upload token management tools

## Problem

Upload tokens are required for CI/CD pipelines to push coverage reports to Codecov. Managing these tokens currently requires:

- Manual access to Codecov web UI
- Manual rotation when tokens are compromised
- No programmatic way to retrieve or regenerate tokens

This creates security and operational challenges, especially for organizations managing many repositories.

## Proposed Solution

Add tools for viewing and managing upload tokens.

### 1. `get_upload_token`

Retrieve the curr

[Read the thread](https://github.com/egulatee/mcp-server-codecov/issues/93) · 2026-02-12 · open · 0 comments

The remaining reports are on [the project's issue tracker](https://github.com/egulatee/mcp-server-codecov/issues).