Ext Ops Panel
Open dashboard
Comparison

Casely vs SmartBear MCP

Casely is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑26.

Casely is a plugin bundle for AI coding tools published by John Wayne. No marketplace we read lists it any more. SmartBear MCP is an MCP server published by smartbear.com. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-26. 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
MarketplaceCaselySmartBear MCP
Community marketplace johnwayneeee/casely-qa-skill Removed on 2026-10-26
Version: 2.4.0
Forks (GitHub): 0
Stars (GitHub): 11
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.42.0
Downloads/month (npm): 45 350
Downloads/week (npm): 4 476
Forks (GitHub): 51
Stars (GitHub): 44
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:8a64acae01b6
Forks (GitHub): 51
Pulls (Docker Hub): 14 685
Stars (Docker Hub): 0
Stars (GitHub): 44
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

Casely vs SmartBear MCP
FactCaselyno longer listed · SmartBear MCP
Marketplaces that list it (differs)02
Stars (GitHub) (differs)1144
Pulls (Docker Hub) (differs)No figure on Docker Hub14 685
Forks (GitHub) (differs)051
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.atlassian.com/v2/mcp)Remote server or your machine
Transport (differs)Streamable HTTPStreamable HTTP, stdio
Tools it declares (differs)Not published160
Environment variables it asks for (differs)Not published17, secrets among them: 10
Parts of the bundle (differs)4Not a bundle
LicenceMITMIT
Repository (differs)github.com/johnwayneeee/casely-qa-skillgithub.com/smartbear/smartbear-mcp
Changes in the last 7 days (differs)80
First seen (differs)2026-10-232026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 400 (3 days ago)

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 Casely

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • paranoid-qa

    English skills: evidence-disciplined testing framework, Playwright test review, test cases, Jira bug reports

    by Aleksei Kovalev · Plugin bundle

    Listed on: Community GitHub marketplaces · 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

  • 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

  • qa-expert

    QA process setup with AAA test cases, P0-P4 bug tracking, metrics reports, OWASP security testing and third-party handoffs. Use for test planning, approved-batch execution and…

    by daymade · Plugin bundle

    Listed on: Community GitHub marketplaces · 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

  • getlark

    Natural-language end-to-end tests for any software surface, powered by getlark.ai

    by getlark · Plugin bundle

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

Its card, with similar plugins by marketplace

What each says it does

Casely

In its own words, on Community GitHub marketplaces:

Attach requirements or name a Jira issue, add an example of your team's test cases, approve one plan, get a TestRail-ready Excel or CSV file back, plus a runnable Postman collection when the spec describes an API, and bug reports from a trace ID.

SmartBear MCP

In its own words, on Official MCP Registry:

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

How to run each

Casely

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

SmartBear MCP As a remote MCP server

Claude Code
claude mcp add --transport http smartbear-mcp https://bugsnag.mcp.smartbear.com/mcp

Requires: BEARQ_API_TOKEN (secret), BUGSNAG_AUTH_TOKEN (secret), PACT_BROKER_PASSWORD (secret), PACT_BROKER_TOKEN (secret), QTM4J_API_KEY (secret), QTM4J_AUTOMATION_API_KEY (secret), REFLECT_API_TOKEN (secret), SWAGGER_API_KEY (secret), SWAGGER_FUNCTIONAL_TESTING_API_TOKEN (secret), ZEPHYR_API_TOKEN (secret)

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

Only SmartBear MCP has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Casely publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Casely publish no settings it asks for, so we do not compare settings.

What it can do: Casely · What it can do: SmartBear 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. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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