Coverctl MCP Server

Go code coverage analysis tool with MCP server for AI-powered coverage workflows

The short version

Works best on standard Go/Python/JavaScript/Java/Rust projects with conventional layouts. Mock-heavy code or exotic monorepos may need an explicit domains: block in .coverctl.yaml.

• Catches regressions before commit. — Coverage feedback in the agent's edit turn — not minutes after CI fails. The wedge metric is regressions caught pre-commit
• Agent-callable via MCP. — Speaks MCP — the multi-vendor agent-tool standard now governed by Anthropic, OpenAI, Google, Microsoft, AWS. Works with every MCP-capable client today; works with whatever ships next without modification
• Polyglot governance, one config. — One .coverctl.yaml enforces per-domain thresholds across 15 languages. Agents touch any language; coverage tooling must too
• Local-first. — Your source never leaves the machine. Agent calls coverctl over stdio, not over a SaaS API. No account, no upload, no third-party dependency in the agent's reach
• Hardened MCP surface. — Input + output sanitization defends against prompt-injection through test-runner flags and hostile filenames in coverage profiles (Lethal Trifecta)

More MCP options

Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.

Maintainer setup documentation.