browser-test vs SmartBear MCP
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. SmartBear MCP is an MCP server published by smartbear.com. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-27. 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 |  SmartBear MCP | |
|---|---|---|
| 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: 0.42.0 Downloads/month (npm): 45 350 Downloads/week (npm): 4 476 Forks (GitHub): 51 Stars (GitHub): 44 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:8a64acae01b6 Forks (GitHub): 51 Pulls (Docker Hub): 14 701 Stars (Docker Hub): 0 Stars (GitHub): 44 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 · | SmartBear MCP |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 7 | 44 |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 14 701 |
| Forks (GitHub) (differs) | 0 | 51 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP, stdio |
| Tools it declares (differs) | Not published | 160 |
| Environment variables it asks for (differs) | Not published | 17, secrets among them: 10 |
| Parts of the bundle (differs) | 4 | Not a bundle |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/autodesk/claude-browser-test-skills | github.com/smartbear/smartbear-mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 400 (3 days ago) |
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
SmartBear MCP
MCP server for AI access to SmartBear tools, including BugSnag, Reflect, Swagger, PactFlow, QTM4J.
How to run each
browser-test
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
SmartBear MCP As a remote MCP server
claude mcp add --transport http smartbear-mcp https://bugsnag.mcp.smartbear.com/mcpRequires: BEARQ_API_TOKEN (secret), BUGSNAG_AUTH_TOKEN (secret), PACT_BROKER_PASSWORD (secret), PACT_BROKER_TOKEN (secret), QTM4J_API_KEY (secret), QTM4J_AUTOMATION_API_KEY (secret), REFLECT_API_TOKEN (secret), SWAGGER_API_KEY (secret), SWAGGER_FUNCTIONAL_TESTING_API_TOKEN (secret), ZEPHYR_API_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only SmartBear MCP has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of browser-test publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of browser-test publish no settings it asks for, so we do not compare settings.
What it can do: browser-test · What it can do: SmartBear MCP · 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. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.