testops vs SmartBear MCP
testops is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑23.
testops is a plugin bundle for AI coding tools published by AI Hub Contributors. 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-25. 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 | ||
|---|---|---|
| Community marketplace dodobrands/ai-hub | Removed on 2026-10-23 Version: 0.1.1 Forks (GitHub): 8 Stars (GitHub): 8 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 615 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 | testopsno longer listed · | SmartBear MCP |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 8 | 44 |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 14 615 |
| Forks (GitHub) (differs) | 8 | 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) | 1 | Not a bundle |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/dodobrands/ai-hub | github.com/smartbear/smartbear-mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-16 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 400 (35 h 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 testops
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Use TestDino inside Claude Code through the hosted remote MCP server to inspect test runs, debug failing test cases, manage manual tests, and run TestDino audits.
-
allure-testops-mcp io.github.mshegolev/allure-testops-mcp
Allure TestOps MCP — projects, launches, test cases, test results via REST API.
-
Official MCP server for Qase — manage test cases, runs, suites, defects via AI tools.
-
Create and manage test cases, test runs and results in Testiny from your AI assistant.
-
Direct access to Cypress tests results and accessibility reports in your AI workflow.
-
Access Playwright Reports Server data (failures, flakiness, Failure clusters) via the pwrs-cli.
What each says it does
testops
Allure TestOps integration — test cases, launches, defects, test plans, jobs via REST API
SmartBear MCP
MCP server for AI access to SmartBear tools, including BugSnag, Reflect, Swagger, PactFlow, QTM4J.
How to run each
testops
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/mcp
Requires: 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 testops publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of testops publish no settings it asks for, so we do not compare settings.
What it can do: testops · 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.