Pod

Available as Markdown and JSON. Pod is also available over MCP.

Reported issues for codecov by egulatee

Pod holds 16 of 17 GitHub reports that passed its relevance review. This can include external user reports, maintainer-confirmed bugs, and concrete feature gaps. Treat them as evidence to inspect, not a count of distinct defects.

Back to codecov by egulatee.

Most discussed

Add MCP prompts and resources for LobeHub marketplace discovery

Problem

LobeHub marketplace listing currently shows:

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…

Read the thread · 2025-12-21 · closed · 1 comment

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

Context

openclaw-operator#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…

Read the thread · 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:

socat TCP:localhost:3000 STDIO

Without…

Read the thread · 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:

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

Read the thread · 2026-02-17 · 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

Read the thread · 2026-02-13 · closed · 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

Proposed Tool

###…

Read the thread · 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

Proposed Tool

get_coverage_history

Get coverage trend data over time.…

Read the thread · 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

2. Branch Detail

Read the thread · 2026-02-12 · open · 0 comments

Most recent

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

2. Coverage Comparison

Read the thread · 2026-02-12 · closed · 0 comments

Add coverage trend and historical data tools

Problem

Understanding coverage trends over time is crucial for tracking code quality improvements or regressions. Currently, there's no way to:

Proposed Solution

Add a tool to retrieve historical coverage data.

get_coverage_history

Get coverage trend data over time.

{
  name:…

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

### Add branch listing and management tools

## Problem

Users need to discover which branches have coverage data and compare coverage across branches. Currently, you must know the branch name in advance to query coverage via `get_repo_coverage`.

## Proposed Solution

Add a tool to list all branches with coverage data.

### `list_branches`

List all branches that have coverage data.

```typescript
{
  name: "list_branches",
  description: "List all branches in a repository that have coverage data, with basic coverage statistics",…

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

### Add repository configuration management tools

## Problem

Repository configuration (coverage thresholds, status checks, notification settings) can only be managed through the Codecov web UI or via `codecov.yml` file in the repository. There's no programmatic way to:

- View current repository configuration
- Update coverage thresholds
- Configure status checks for PRs
- Manage notification settings

## Proposed Solution

Add tools for viewing and managing repository configuration.

### 1. `get_repository_settings`

View current repository…

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

### Add pull request coverage tools

## Problem

Pull requests are a critical point for code review and quality gates, but there's currently no way to query PR-specific coverage data through the MCP server. Developers need to:

- Check if a PR increases or decreases coverage
- View coverage for only the files changed in a PR
- Compare PR coverage against the base branch
- Make decisions about merging based on coverage impact

## Proposed Solution

Add two new MCP tools for PR coverage analysis:

### 1. `get_pull_request_coverage`…

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

### Add repository activation tool

## Problem

When setting up a new repository in Codecov, the repository must be manually activated through the web UI before it can receive coverage uploads. This creates friction in CI/CD workflows where you want to automatically configure coverage reporting.

**Real-world scenario**: During automated setup of a GitHub repository with coverage reporting, the CI workflow fails because the Codecov repository hasn't been activated yet, even though the upload token is correctly configured.

##…

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

### Add debug logging mode

## Problem
No visibility into API requests/responses when debugging issues. Users can't easily troubleshoot connection problems or see what's being sent to Codecov.

## Proposed Solution
Add optional debug mode via environment variable:
```typescript
private debug: boolean = process.env.CODECOV_DEBUG === 'true';

private log(message: string, data?: any): void {
  if (this.debug) {
    console.error(`[CodecovClient] ${message}`, data || '');
  }
}

Log requests/responses with sensitive data…

Read the thread · 2025-12-22 · open · 0 comments

Add MCP prompts and resources for LobeHub marketplace discovery

Problem

LobeHub marketplace listing currently shows:

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…

Read the thread · 2025-12-21 · closed · 0 comments

The remaining reports are on the project's issue tracker.