Covdbg

covdbg-mcp

MCP server for covdbg: C++ code coverage on Windows for AI agents. Run tests, find uncovered code, and add targeted tests. No rebuild required.

covdbg measures coverage of the Windows x64 binaries you already build, using their PDB debug information. It works like a debugger: it starts your executable, reads the PDB, and places lightweight probes while the program runs. The MCP server is built into the covdbg executable (since v1.3.0) and is started with covdbg mcp.

This repository holds the MCP registry metadata (server.json, glama.json) and the MCP Bundle manifest (manifest.json) for covdbg. The server itself ships with covdbg.

What an agent can do

1. Run coverage on a test executable without rebuilding it.
2. Rank files by uncovered lines.
3. Read the uncovered code with surrounding context.
4. Add a focused test, re-run it, and confirm the gap is closed.
5. Query and merge coverage databases (.covdb) with read-only SQL.

Requirements

• Windows x64
• covdbg 1.3.0 or newer
• An executable with PDB debug symbols (MSVC or any PDB-producing toolchain)
• A one-time covdbg login (covdbg 1.4 and newer sign in to one team, and runs need a seat in that team), or COVDBG_PROJECT_TOKEN for CI
• A .covdbg.yaml next to the target executable, or a config_path passed to run (see the configuration reference)

Install covdbg

• Installer (recommended): installer.msi. It installs to %LocalAppData%\Programs\Liasoft\covdbg and adds that directory to your user PATH.
• Portable: portable.zip. Extract it anywhere and add the directory to your PATH yourself.

Then open a new terminal and sign in:

covdbg --version
covdbg login

Sign-in is team-scoped: in the browser you choose one team (your personal team, or a team you own or hold a seat in), and the agent's runs are licensed for that team. Use covdbg login --team <slug> to choose it up front, and covdbg whoami to see which team is active. In CI, COVDBG_PROJECT_TOKEN decides by the token's team.

Client setup

The server uses stdio transport. Start it from your project directory, or pass --workspace <dir>.

Claude Code

From the project directory:

claude mcp add covdbg -- covdbg mcp

Or add a project .mcp.json:

{
  "mcpServers": {
    "covdbg": {
      "command": "covdbg",
      "args": ["mcp"]
    }
  }
}

VS Code

.vscode/mcp.json:

{
  "servers": {
    "covdbg": {
      "type": "stdio",
      "command": "covdbg",
      "args": ["mcp", "--workspace", "${workspaceFolder}"]
    }
  }
}

Cursor

.cursor/mcp.json:

{
  "mcpServers": {
    "covdbg": {
      "command": "covdbg",
      "args": ["mcp"]
    }
  }
}

Claude Desktop (MCP Bundle)

1. Download covdbg.mcpb from the latest release.
2. Open it with Claude Desktop, or drag it into Settings → Extensions.
3. Set the following:
   • covdbg executable: the path to covdbg.exe. The default is the MSI install location.
   • Workspace: your project directory.
   • Project token: optional. Leave it empty if you have run covdbg login; runs are then licensed for the team you signed in to (see covdbg whoami).

The bundle does not contain covdbg itself. It launches your installed covdbg.exe, so covdbg updates take effect without a new bundle.

Tools

Limits and behavior

• Run session IDs start with run-; coverage session IDs start with covdb-.
• At most 8 runs in flight and 32 open coverage sessions.
• wait_run blocks for at most 30 seconds. If it reports stillRunning, call it again.
• Run outcomes are success, no_functions_to_track, license_failure, or error.
• covdbg's exit code does not carry the target's exit code, so check test results separately.

Environment variables

Documentation

• MCP Server
• Quick Start Using AI
• CLI Command Reference
• Data and Telemetry

Publishing (maintainers)

Keep version in manifest.json and server.json, and the release tag in the server.json package URL, in sync.

1. Build the bundle. .mcpbignore limits it to manifest.json, icon.png and LICENSE:

   npx @anthropic-ai/mcpb validate manifest.json
   npx @anthropic-ai/mcpb pack . covdbg.mcpb
   

2. Create the GitHub release v<version> and upload covdbg.mcpb as an asset.

3. Put the bundle's hash into fileSha256 in server.json:

   (Get-FileHash covdbg.mcpb -Algorithm SHA256).Hash.ToLower()
   

4. Publish to the MCP registry. The com.covdbg/* namespace uses DNS authentication on covdbg.com:

   mcp-publisher login dns --domain covdbg.com --private-key <key>
   mcp-publisher publish
   

5. Glama picks up glama.json from the repository.

License

The metadata in this repository is licensed under the Apache License 2.0. covdbg itself is licensed separately, with Free, Team, and Enterprise plans. See covdbg.com and the Licensing FAQ.