Official description7 sourcesMCP servers8d ago
avansaber/tailtest-cline
Adversarial test gen
View on GitHub ↗Direct link · no redirect page
Config template (adjust for your client)
claude mcp add tailtest-cline -- npx -y tailtest-cline
A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
- Star count
- 1 ★ · avansaber/tailtest-cline · read from the repository page · (checked 2026-10-16 20:00:20)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
- Score
- score 703 · 1 ★ · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
avansaber/tailtest-cline；first catalogued 2026-10-09；last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.Third-party quality signals
tailtest-cline -- AI software testing for Cline (8+ editors)
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
> You build. Claude builds. tailtest makes sure it works -- across 8+ editors at once.
**tailtest-cline** is the open-source AI software testing layer for Cline, the autonomous coding agent that runs across 8+ editors (VS Code, Cursor, JetBrains IDEs, Antigravity, Zed, Neovim, VSCodium, Windsurf, plus the Cline CLI). MCP-driven test generation: every time Cline edits a file, tailtest's MCP server picks up the change, generates production-shaped scenarios via the R1-R15 rule layer, runs them, and returns structured failure data to Cline. Adversarial mode (R15) included from day one.
Open source (MIT), no telemetry, no SaaS account. Same R1-R15 rule layer + adversarial mode as the Claude Code, Cursor, and Codex CLI variants -- 1,234 plugin tests total across the four hosts.
**Read more on tailtest.com · Platform overview · Agent-edit testing deep dive · Cline docs**
**Cline reach:** VS Code, Cursor, JetBrains IDEs, Antigravity, Zed, Neovim, VSCodium, Windsurf, plus the Cline CLI. One plugin, eight-plus editors.
What's different from the other variants
Cline does not have hooks (Claude Code's PostToolUse, Cursor's afterFileEdit, Codex's Stop). Instead, tailtest-cline uses three Cline-native primitives:
- **.clinerules/** carries the rule layer (R1-R14 + R15 adversarial mode)
- **tailtest-mcp server** (this repo) provides structured tools for the agent: tailtest_setup, tailtest_scenario_plan, tailtest_classify_failures, tailtest_pick_template, tailtest_ping
- **Memory Bank** (tailtestContext.md) holds the per-project profile across Cline sessions
The deterministic policy (depth tiers, R15 adversarial counts, framework templates, file paths) lives in MCP server code rather than rule text. The agent calls the tools when it needs scaffolding rather than relying on rule recall over long sessions.
Install
Three install paths:
1. Cline MCP Marketplace (recommended; one click)
Open Cline's Extensions panel inside your IDE. Search tailtest. Click install. Cline clones, installs deps, registers the server in cline_mcp_settings.json automatically.
2. Direct GitHub install
Paste https://github.com/avansaber/tailtest-cline into Cline's MCP server install dialog. Cline does the same clone + install + register flow.
3. Manual cline_mcp_settings.json edit
First run
After install, type in Cline chat: **"set up tailtest in this project"**.
Cline calls tailtest_setup. The tool detects language / framework / runner, writes .clinerules/, writes .clinerules/workflows/, seeds memory-bank/tailtestContext.md, and initialises .tailtest/config.json + .tailtest/session.json. Idempotent: existing files preserved.
**Important:** Cline does not auto-reload .clinerules mid-conversation. Start a new conversation (or reload the window) to activate.
Two operating modes
Manual mode (default)
You invoke the test cycle explicitly:
- /tailtest-test -- run the cycle on a specific file
- /tailtest hunt -- one-shot adversarial pass on a specific file
**tailtest-cline** is the open-source AI software testing layer for Cline, the autonomous coding agent that runs across 8+ editors (VS Code, Cursor, JetBrains IDEs, Antigravity, Zed, Neovim, VSCodium, Windsurf, plus the Cline CLI). MCP-driven test generation: every time Cline edits a file, tailtest's MCP server picks up the change, generates production-shaped scenarios via the R1-R15 rule layer, runs them, and returns structured failure data to Cline. Adversarial mode (R15) included from day one.
Open source (MIT), no telemetry, no SaaS account. Same R1-R15 rule layer + adversarial mode as the Claude Code, Cursor, and Codex CLI variants -- 1,234 plugin tests total across the four hosts.
**Read more on tailtest.com · Platform overview · Agent-edit testing deep dive · Cline docs**
**Cline reach:** VS Code, Cursor, JetBrains IDEs, Antigravity, Zed, Neovim, VSCodium, Windsurf, plus the Cline CLI. One plugin, eight-plus editors.
What's different from the other variants
Cline does not have hooks (Claude Code's PostToolUse, Cursor's afterFileEdit, Codex's Stop). Instead, tailtest-cline uses three Cline-native primitives:
- **.clinerules/** carries the rule layer (R1-R14 + R15 adversarial mode)
- **tailtest-mcp server** (this repo) provides structured tools for the agent: tailtest_setup, tailtest_scenario_plan, tailtest_classify_failures, tailtest_pick_template, tailtest_ping
- **Memory Bank** (tailtestContext.md) holds the per-project profile across Cline sessions
The deterministic policy (depth tiers, R15 adversarial counts, framework templates, file paths) lives in MCP server code rather than rule text. The agent calls the tools when it needs scaffolding rather than relying on rule recall over long sessions.
Install
Three install paths:
1. Cline MCP Marketplace (recommended; one click)
Open Cline's Extensions panel inside your IDE. Search tailtest. Click install. Cline clones, installs deps, registers the server in cline_mcp_settings.json automatically.
2. Direct GitHub install
Paste https://github.com/avansaber/tailtest-cline into Cline's MCP server install dialog. Cline does the same clone + install + register flow.
3. Manual cline_mcp_settings.json edit
First run
After install, type in Cline chat: **"set up tailtest in this project"**.
Cline calls tailtest_setup. The tool detects language / framework / runner, writes .clinerules/, writes .clinerules/workflows/, seeds memory-bank/tailtestContext.md, and initialises .tailtest/config.json + .tailtest/session.json. Idempotent: existing files preserved.
**Important:** Cline does not auto-reload .clinerules mid-conversation. Start a new conversation (or reload the window) to activate.
Two operating modes
Manual mode (default)
You invoke the test cycle explicitly:
- /tailtest-test -- run the cycle on a specific file
- /tailtest hunt -- one-shot adversarial pass on a specific file
- Source
- awesome · https://github.com/avansaber/tailtest-cline
- Browse by field
- MCP servers
- Traction
- 1 ★
- added
- yesterday
More in MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.