testops vs Qase Test Management
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. Qase Test Management is an MCP server published by qase.io. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). 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 |  Qase Test Management | |
|---|---|---|
| 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: 3.0.3 Downloads/month (npm): 7 170 Downloads/week (npm): 2 119 Forks (GitHub): 10 Stars (GitHub): 37 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 3.0.3 Downloads/month (npm): 7 170 Downloads/week (npm): 2 119 Forks (GitHub): 10 Stars (GitHub): 37 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 · | Qase Test Management |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 8 | 37 |
| Forks (GitHub) (differs) | 8 | 10 |
| Last release (differs) | Not published | 2026-10-28 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 1 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/dodobrands/ai-hub | github.com/qase-tms/qase-mcp-server |
| Changes in the last 7 days (differs) | 2 | 4 |
| First seen (differs) | 2026-10-16 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded less than an hour 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 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.
-
MCP server for AI access to SmartBear tools, including BugSnag, Reflect, Swagger, PactFlow, QTM4J.
-
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
Qase Test Management
Official MCP server for Qase — manage test cases, runs, suites, defects via AI tools.
How to run each
testops
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Qase Test Management As a remote MCP server
claude mcp add --transport http qase-test-management https://mcp.qase.io/mcpRequires: QASE_API_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Qase Test Management 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
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: Qase Test Management · 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. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.