browser-test vs TesterArmy
browser-test is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑22.
browser-test is a plugin bundle for AI coding tools published by Brian Dueck. No marketplace we read lists it any more. TesterArmy is an MCP server published by tester-army. 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 |  TesterArmy | |
|---|---|---|
| Community marketplace autodesk/claude-browser-test-skills | Removed on 2026-10-22 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 7 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Forks (GitHub): 6 Stars (GitHub): 72 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 | browser-testno longer listed · | TesterArmy |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 7 | 72 |
| Forks (GitHub) (differs) | 0 | 6 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (tester.army/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 4 | 2 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/autodesk/claude-browser-test-skills | github.com/tester-army/cli |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 32 h ago, requires a key |
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 browser-test
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Playwright Pro turns your AI coding agent into a senior test automation engineer. Instead of generating tutorial-quality tests with brittle CSS selectors, Playwright Pro enforces…
-
pw
Production-grade Playwright testing toolkit. 9 skills, 3 agents, 55 templates, plus optional (manually enabled) TestRail/BrowserStack integrations. Generate tests, fix flaky…
-
Browser automation via Playwright CLI for testing, screenshots, and interaction workflows
-
Vibe Test — Browser Testing Agent
Code-aware browser testing agent — 14 Playwright tools for AI code editors via MCP
-
Playwright automation toolkit with MCP integration, specialized agent for browser control, and best practice skills
-
Browser automation + recorded QA sessions for Claude Code: skills, JTBD subagents, and /canary:verify | run | session | review commands.
What each says it does
browser-test
E2E browser test pipeline for Claude Code: author, refine, compile, and run Playwright tests using browser automation
TesterArmy
Agents that test your web and mobile app like real users, on every pull request.
How to run each
browser-test
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
TesterArmy As a remote MCP server
claude mcp add --transport http testerarmy https://tester.army/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only TesterArmy has a remote endpoint we check. How we check endpoints
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: browser-test · What it can do: TesterArmy · 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.