Ext Ops Panel
Open dashboard
Comparison

SmartBear MCP vs io.github.worklore/worklore

SmartBear MCP is an MCP server published by smartbear.com. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). io.github.worklore/worklore is an MCP server published by worklore. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
MarketplaceSmartBear MCPio.github.worklore/worklore
Official MCP Registry Listed
Version: 0.42.0
Downloads/month (npm): 47 525
Downloads/week (npm): 10 500
Forks (GitHub): 50
Stars (GitHub): 44
Not marked · First seen
Listed
Version: 0.7.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Docker MCP Catalog Listed
Version: sha256:8a64acae01b6
Forks (GitHub): 50
Pulls (Docker Hub): 14 339
Stars (Docker Hub): 0
Stars (GitHub): 44
Not marked · First seen
Not listed

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

SmartBear MCP vs io.github.worklore/worklore
FactSmartBear MCPio.github.worklore/worklore
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)44 (better)0 (worse)
Pulls (Docker Hub) (differs)14 339No figure on Docker Hub
Forks (GitHub) (differs)50 (better)0 (worse)
Last release (differs)Not published2026-10-15
Where it runs (differs)Remote server or your machineRemote server (worklore.dev/mcp)
Transport (differs)Streamable HTTP, stdioStreamable HTTP
Tools it declares (differs)160Not published
Environment variables it asks for (differs)17, secrets among them: 10Not published
Licence (differs)MITNot stated
Repository (differs)github.com/smartbear/smartbear-mcpgithub.com/worklore/worklore-mcp
Changes in the last 7 days (differs)01
First seen2026-10-112026-10-11
Endpoint at the last check (differs)not checked yetResponded 41 h ago

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

SmartBear MCP

In its own words, on Official MCP Registry:

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

io.github.worklore/worklore

In its own words, on Official MCP Registry:

Search worklore stories and x-ray any skill or story capability tier (T0-T4) before you run it.

How to run each

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)

io.github.worklore/worklore As a remote MCP server

Claude Code
claude mcp add --transport http worklore https://worklore.dev/mcp

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

Only io.github.worklore/worklore has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of io.github.worklore/worklore publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of io.github.worklore/worklore publish no settings it asks for, so we do not compare settings.

What it can do: SmartBear MCP · What it can do: io.github.worklore/worklore · Compare two other plugins

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