Skip to main content
Glama
Sign In
coverage-orchestrator-mcp

coverage-orchestrator-mcp

by markgregg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to coverage-orchestrator-mcp

No user-submitted related servers found.

    Related Servers

    • testmcp

      r-marques
      A
      license
      A
      quality
      D
      maintenance
      Wraps existing test frameworks (Jest, Vitest, Pytest) and exposes structured, LLM-optimized results via MCP tools with progressive disclosure and diff-aware execution.
      11
      1
      MIT

    • test-unslop

      fikrifirmanf
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables coding agents to deterministically audit test files for fake or fragile tests (no assertions, tautological or swallowed assertions, focused/skipped tests, fixed sleeps, real network calls) and to run the project's actual test runner, treating an exit-0 run with zero tests as a failure and flagging changed source files that lack test coverage.
      724 npm
      MIT

    • io.github.morluto/flameox

      HelgaRoux
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables coding agents to coordinate local profilers, benchmark tools, trace processors, and explicit targets into bounded runtime evidence, including observed inputs, execution provenance, typed findings, coverage, and limitations. It supports analysis and capture through named MCP tools without workspace setup or project configuration.
      -
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    B3.1/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: setup, fetching uncovered code, running tests, verifying targets, and orchestrating improvements. No two tools serve overlapping functions.

    Naming Consistency5/5

    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.

    Tool Count5/5

    Five tools is appropriate for a coverage orchestration server, covering the essential workflow without unnecessary complexity. The scope is well-defined.

    Completeness5/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources