Cypress vs Qase Test Management
Cypress is a plugin bundle for AI coding tools published by cypress-io. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-community, Community GitHub marketplaces). 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-27. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Cypress |  Qase Test Management |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.1.0 Forks (GitHub): 4 Stars (GitHub): 47 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 3.0.2 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.2 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 | Cypress | Qase Test Management |
|---|---|---|
| Marketplaces that list it | 2 | 2 |
| Stars (GitHub) (differs) | 47 (better) | 37 (worse) |
| Forks (GitHub) (differs) | 4 (worse) | 10 (better) |
| Last release (differs) | 2026-10-23 (worse) | 2026-10-27 (better) |
| 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) | 5 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/cypress-io/ai-toolkit | github.com/qase-tms/qase-mcp-server |
| Changes in the last 7 days (differs) | 1 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 5 days ago, requires a key |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Cypress
Create, update, and fix Cypress tests. Connect to Cypress Cloud to see test results and use data to manage your test suite.
Qase Test Management
Official MCP server for Qase — manage test cases, runs, suites, defects via AI tools.
How to run each
Cypress As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install cypress@claude-communityQase 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 Cypress publish no settings it asks for, so we do not compare settings.
What it can do: Cypress · What it can do: Qase Test Management · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.