qa vs Qlane
qa is a plugin bundle for AI coding tools published by Browser Use. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Qlane is an MCP server published by qlane.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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 |  Qlane | |
|---|---|---|
| Community marketplace browser-use/plugins | Listed Version: 0.1.1 Forks (GitHub): 9 Stars (GitHub): 24 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 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 | qa | Qlane |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 24 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 9 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (mcp-eu.qlane.ai/api/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/browser-use/plugins | github.com/qlaneai/agent-plugin |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | not checked yet |
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
qa
QA-test a website or app and return a 1-5 quality score with evidence. Drives a Browser Use cloud browser and tunnels localhost automatically. Run as /qa <url-or-localhost-port>. Requires the browser-harness CLI (the skill installs it itself if missing).
Qlane
AI QA that runs your app in a browser on every pull request: projects, test targets, test cases.
How to run each
qa As a Claude Code plugin
/plugin marketplace add browser-use/plugins
/plugin install qa@browser-useQlane As a remote MCP server
claude mcp add --transport http qlane https://mcp-eu.qlane.ai/api/mcpCommands 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
Neither one's marketplaces publish the settings it asks for.
What it can do: qa · What it can do: Qlane · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.