tailtest-cline
Related Servers
Alternatives to tailtest-cline
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceOpenTester 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.29MIT

Pluswithai MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to run tests, read failures, push new tests, and schedule them, either by connecting directly to a hosted endpoint or via a local stdio bridge.17 npmMIT- AlicenseNot gradedqualityBmaintenanceIntegrates 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
- AlicenseAqualityBmaintenanceEnables AI agents to run a project's pytest, unittest, jest, or vitest suites and get back compact structured results with trimmed tracebacks, collection errors kept apart from real failures, and the slowest tests. Agents can then re-run just the failures, expand one failure with local variables, repeatedly execute a single test to judge flakiness, and inspect Python coverage gaps, all under a hard timeout that kills the whole process tree.7MIT
- AlicenseNot gradedqualityBmaintenanceEnables users to make AI coding agents prove their work with passing tests before finishing, snapshot every edit so any step can be undone, and trim noisy tool output to save tokens. Runs locally with no telemetry and works with Claude Code, Codex and OpenCode.63 PyPI4Apache 2.0
- AlicenseAqualityBmaintenanceProvides 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.9Apache 2.0
TDQS
Scored across 5 tools
Each tool serves a distinct purpose: setup, health check, template selection, scenario planning, and failure classification. There is no overlap or ambiguity between them.
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.
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.
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.