Ext Ops Panel
Open dashboard
Comparison

qikly vs Testorim

qikly is an MCP server published by gal-a. Marketplaces we read that list it: 1 (Official MCP Registry). Testorim is an MCP server published by sallar-ba. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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

Where each is published
MarketplaceqiklyTestorim
Official MCP Registry Listed
Version: 0.6.0
Downloads/month (PyPI): 3 095
Downloads/week (PyPI): 196
Forks (GitHub): 0
Stars (GitHub): 17
Not marked · First seen
Listed
Version: 0.4.1
Downloads/month (npm): 784
Downloads/week (npm): 20
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

qikly vs Testorim
FactqiklyTestorim
Marketplaces that list it11
Stars (GitHub) (differs)17No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last release (differs)2026-10-19Not published
Where it runs (differs)On your machine (qikly)On your machine (@testorim/cli)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 02, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/gal-a/qiklyNot stated
Changes in the last 7 days (differs)20
First seen2026-10-112026-10-11

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

qikly

In its own words, on Official MCP Registry:

Generates tests from acceptance criteria, then converges code with an agent that never sees them.

Testorim

In its own words, on Official MCP Registry:

AI browser tests from your coding agent: a verdict, failing steps, report, video and trace.

How to run each

qikly As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio qikly -- uvx --from "qikly[mcp]==0.6.0" qikly-mcp qikly

Testorim As a local MCP server: npm package

Claude Code
claude mcp add --env "TESTORIM_API_KEY=<YOUR_TESTORIM_API_KEY>" --transport stdio testorim -- npx -y @testorim/cli mcp

Requires: TESTORIM_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only qikly asks for

  • QIKLY_PROJECT_ROOT

Only Testorim asks for

  • TESTORIM_API_KEY (secret)
  • TESTORIM_API_URL

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: qikly · What it can do: Testorim · Compare two other plugins

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.

Where the data comes from: how the catalog is built