Skip to main content
Glama
barissozudogru

test-intel-mcp

by barissozudogru
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to test-intel-mcp

No user-submitted related servers found.

    Related Servers

    • ast-impact-mapper-mcp

      vola-trebla
      A
      license
      A
      quality
      D
      maintenance
      MCP server that analyzes TypeScript/JavaScript codebases via AST parsing and dependency graph tracing to identify affected tests, detect dead code, circular dependencies, and trace import chains, enabling AI agents to run only relevant tests.
      15
      45 npm
      MIT

    • test-coverage-mcp

      goldbergyoni
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that provides instant, token-efficient test coverage data for any programming language, allowing agents to query coverage summaries and track session progress.
      42 npm
      41
      MIT

    • coverage-mcp

      ProgrammerDream
      F
      license
      A
      quality
      D
      maintenance
      MCP server for Java branch coverage analysis using JaCoCo. Enables agent-style coverage feedback with per-test-class granularity and uncovered line identification.
      2
      -

    • dotnet-coverage-mcp

      Hyeonu-Cha
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that gives AI assistants direct access to .NET test-coverage tooling, enabling them to run tests, parse Cobertura XML, identify uncovered branches, diff coverage between runs, and append test code.
      1
      MIT

    • Chisel

      IronAdamant
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for test impact analysis and code intelligence. Maps tests to code and git history to determine impacted tests, risk scores, and ownership for AI coding agents.
      3
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 4 tools

    Disambiguation4/5

    Each tool has a distinct focus: generating test cases, parsing coverage reports, finding untested functions, and analyzing complexity. However, find_untested_functions and get_function_complexity both aim at identifying functions that need testing, which could cause some initial confusion.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern, e.g., suggest_test_cases, analyze_test_coverage, find_untested_functions, get_function_complexity. This makes the toolset predictable and easy for an agent to navigate.

    Tool Count5/5

    Four tools is well-scoped for a testing intelligence server, with each tool serving a clear and non-redundant purpose. There is no bloat, and the count feels sufficient for the stated domain.

    Completeness4/5

    The set covers a natural workflow of testing intelligence: generating tests, assessing coverage, identifying untested functions, and prioritizing via complexity. This is a solid read-only surface, though additional tools like listing existing test files or summarizing coverage trends could round it out further.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources