tdd vs Vibe Test — Browser Testing Agent
tdd is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑23.
tdd is a plugin bundle for AI coding tools published by iowarp. No marketplace we read lists it any more. Vibe Test — Browser Testing Agent is an MCP server published by AishwaryShrivastav. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-29. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Vibe Test — Browser Testing Agent | |
|---|---|---|
| Community marketplace iowarp/clio-kit | Removed on 2026-10-16 Version: 0.4.0 Forks (GitHub): 5 Stars (GitHub): 8 Not marked · First seen |
Not listed |
| Community marketplace iowarp/clio-coder | Removed on 2026-10-23 Version: 0.4.1 Forks (GitHub): 5 Stars (GitHub): 8 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.4.6 Downloads/month (npm): 722 Downloads/week (npm): 73 Forks (GitHub): 0 Stars (GitHub): 17 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | tddno longer listed · | Vibe Test — Browser Testing Agent |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 8 | 17 |
| Forks (GitHub) (differs) | 5 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (vibe-testing) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | Not published | 2 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/iowarp/clio-coder | github.com/aishwaryshrivastav/vibe-testing |
| Changes in the last 7 days (differs) | 3 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of tdd
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Implement behavior through a red-green-refactor loop.
-
test-driven-development
Drives features and bug fixes test-first and reviews tests; not CI, build or test-runner config.
-
Test-driven development methodology with red-green-refactor cycles and code review
-
Test-driven development methodology with red-green-refactor cycles and code review
-
PLAN/ACT/EVAL workflow, specialist agents, and reusable skills for systematic TDD development
-
AAID (Augmented AI Development) - TDD workflow enforcing disciplined RED/GREEN/REFACTOR cycles with developer-maintained architectural control
What each says it does
tdd
Builds a feature or fix test-first, red to green at pre-agreed public seams, one vertical slice at a time. Not for designing benchmark criteria; use experiment-protocol.
Vibe Test — Browser Testing Agent
Code-aware browser testing agent — 14 Playwright tools for AI code editors via MCP
How to run each
tdd
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Vibe Test — Browser Testing Agent As a local MCP server: npm package
claude mcp add --transport stdio vibe-testing -- npx -y vibe-testingCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: tdd · What it can do: Vibe Test — Browser Testing Agent · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.