Comparison

testops vs io.github.mshegolev/allure-testops-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. io.github.mshegolev/allure-testops-mcp is an MCP server published by mshegolev. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). 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

Where each is published
Marketplace	testops	io.github.mshegolev/allure-testops-mcp
Community marketplace dodobrands/ai-hub	Removed on 2026-10-23 Version: 0.1.1 Forks (GitHub): 8 Stars (GitHub): 8 Not marked · First seen 2026-10-16	Not listed
Official MCP Registry	Not listed	Listed Version: 0.9.3 Downloads/month (PyPI): 421 Downloads/week (PyPI): 136 Forks (GitHub): 1 Stars (GitHub): 3 Not marked · First seen 2026-10-11
PyPI (MCP servers)	Not listed	Listed Version: 0.9.3 Downloads/month (PyPI): 421 Downloads/week (PyPI): 136 Forks (GitHub): 1 Stars (GitHub): 3 Not marked · First seen 2026-10-12

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

testops vs io.github.mshegolev/allure-testops-mcp
Fact	testopsno longer listed · 2026-10-23	io.github.mshegolev/allure-testops-mcp
Marketplaces that list it (differs)	0	2
Stars (GitHub) (differs)	8	3
Forks (GitHub) (differs)	8	1
Last release	Not published	Not published
Where it runs (differs)	Installs as a plugin bundle	On your machine (allure-testops-mcp)
Transport (differs)	Not stated	stdio
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/mshegolev/allure-testops-mcp
Changes in the last 7 days (differs)	2	0
First seen (differs)	2026-10-16	2026-10-11

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.

testdino

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.

by TestDino · Plugin bundle

Listed on: Claude Code: claude-plugins-community · Describes nearly the same job
SmartBear MCP

MCP server for AI access to SmartBear tools, including BugSnag, Reflect, Swagger, PactFlow, QTM4J.

by smartbear.com · MCP server

Listed on: Official MCP Registry, Docker MCP Catalog · Describes nearly the same job
Qase Test Management

Official MCP server for Qase — manage test cases, runs, suites, defects via AI tools.

by qase.io · MCP server

Listed on: Official MCP Registry · Describes nearly the same job
Testiny Test Management

Create and manage test cases, test runs and results in Testiny from your AI assistant.

by testiny.io · MCP server

Listed on: Official MCP Registry · Describes nearly the same job
Cypress Cloud MCP

Direct access to Cypress tests results and accessibility reports in your AI workflow.

by mcp.cypress.io · MCP server

Listed on: Official MCP Registry · Describes nearly the same job
Playwright Reports

Access Playwright Reports Server data (failures, flakiness, Failure clusters) via the pwrs-cli.

by CyborgTests · Plugin bundle

Listed on: Community GitHub marketplaces · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

testops

In its own words, on Community GitHub marketplaces:

Allure TestOps integration — test cases, launches, defects, test plans, jobs via REST API

io.github.mshegolev/allure-testops-mcp

In its own words, on Official MCP Registry:

Allure TestOps MCP — projects, launches, test cases, test results via REST API.

How to run each

testops

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

io.github.mshegolev/allure-testops-mcp As a local MCP server: PyPI package

Claude Code

claude mcp add --env "ALLURE_TOKEN=<YOUR_ALLURE_TOKEN>" --env "ALLURE_URL=<YOUR_ALLURE_URL>" --transport stdio allure-testops-mcp -- uvx allure-testops-mcp

Requires: ALLURE_TOKEN (secret), ALLURE_URL

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

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: io.github.mshegolev/allure-testops-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. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on 2026-10-25. We publish no contact details for plugin publishers.