coverage-orchestrator-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODE_TREE_MCP_ARGS | No | Additional arguments for code-tree-mcp command | |
| CODE_TREE_MCP_COMMAND | No | Command to run code-tree-mcp (default: 'npx code-tree-mcp') |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ensure_coverage_setupC | Ensure the target workspace has runnable coverage commands and coverage dependencies. |
| run_tests_with_coverageC | Run tests and coverage in the target workspace and collect failures plus artifact paths. |
| fetch_uncovered_codeC | Import LCOV into code-tree-mcp and fetch ranked uncovered symbols. |
| verify_coverage_targetC | Compare current coverage metrics against requested thresholds. |
| improve_test_coverage_orchestratorC | Drive the full iterative coverage improvement loop and produce prioritized next actions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clear, distinct purpose: setup, fetching uncovered code, running tests, verifying targets, and orchestrating improvements. No two tools serve overlapping functions.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., ensure_coverage_setup, fetch_uncovered_code, verify_coverage_target), making them predictable and easy to differentiate.
Five tools is appropriate for a coverage orchestration server, covering the essential workflow without unnecessary complexity. The scope is well-defined.
The tool set covers the full lifecycle: setup, running tests, fetching uncovered code, verification against thresholds, and orchestration of iterative improvements. No obvious gaps for the intended purpose.