Skip to main content
Glama
avansaber

tailtest-cline

by avansaber
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to tailtest-cline

No user-submitted related servers found.

    Related Servers

    • OpenTester

      kznr02
      A
      license
      Not graded
      quality
      C
      maintenance
      OpenTester is a testing execution engine designed for AI coding tools (Claude Code, Cursor, OpenCode, etc.). It provides a unified DSL format and MCP interface, enabling Agents to generate, execute, and manage test cases, achieving an automated "code-test-fix" workflow.
      28
      MIT
    • Qlane MCP by qlaneai

      Qlane MCPofficial

      qlaneai
      A
      license
      Not graded
      quality
      A
      maintenance
      Integrates Qlane test management into AI coding editors, enabling agents to view projects, test targets, and test case counts, and plan tests for local diffs.
      MIT

    • testing-toolkit-mcp

      byreshb
      A
      license
      A
      quality
      A
      maintenance
      Provides coding agents with visibility into test health through tools for flaky test detection, test quality linting, and LLM evaluation harness, enabling them to triage failures, review test quality, and check prompt changes for regressions.
      9
      Apache 2.0

    • rush

      jamesdsizemore
      A
      license
      C
      quality
      A
      maintenance
      Agentic code-quality CLI and stdio MCP server that runs real Python and JS/TS quality engines (Ruff, pytest, ESLint, Prettier, Vitest, etc.) for linting, testing, and reviewing code.
      79
      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

    A4.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool serves a distinct purpose: setup, health check, template selection, scenario planning, and failure classification. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tools follow a consistent snake_case pattern with the prefix 'tailtest_' and a verb_noun structure (e.g., tailtest_classify_failures, tailtest_pick_template). No deviations.

    Tool Count5/5

    With 5 tools, the server is tightly scoped to test analysis and scaffolding. Each tool earns its place without being too few or too many for the domain.

    Completeness4/5

    The tools cover setup, health, template selection, scenario planning, and failure classification. While not a full test framework, it appears complete for its intended planning/analysis purpose. Minor gap: no tool for running tests or generating code.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources