官方说明7 个来源MCP 服务8 天前
avansaber/tailtest-cline
Adversarial test gen
在 GitHub 查看 ↗直链 · 无中转页
配置模板（请按你的客户端调整）
claude mcp add tailtest-cline -- npx -y tailtest-cline
这是根据仓库名生成的可粘贴骨架，命令行参数与包名请以该项目 README 为准。
- ★ 数取值
- 1 ★ · avansaber/tailtest-cline · 取自该仓库的 GitHub 页面 · （2026-10-16 20:00:20 核对）
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单（我们从中收集的条目之一） · 条目类型：MCP 服务
- 收录与活跃
- 收录于 2026-10-09 · 最近见到 2026-10-16 · 共见到 32 次 · 被 7 个来源列出
- 评分构成
- 综合分 703 · 1 ★ · 7 个来源 · mcp
常见问题（答案都来自我们的记录）
怎么安装？
我们【没有】从该仓库取到安装命令（我们的 install 覆盖率只有约 4%）。请看它的 README 或 releases 页。
它适合谁 / 用来做什么？
我们把它归在这些标签下: MCP 服务。标签来自条目自身，不是我们强加的分类。
谁维护它、还在更新吗？
仓库
avansaber/tailtest-cline；我们收录于 2026-10-09；最近见到 2026-10-16。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。第三方质量标记
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
- 来源
- awesome · https://github.com/avansaber/tailtest-cline
- 按领域浏览
- MCP 服务
- Traction
- 1 ★
- 收录于
- 昨天
更多MCP 服务
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。