Comparison

super-claude-for-sap vs SmartBear MCP

super-claude-for-sap is a plugin bundle for AI coding tools published by babamba2. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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-28. 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
Marketplace	super-claude-for-sap	SmartBear MCP
Claude Code: claude-plugins-community	Listed Version: 0.6.16 Forks (GitHub): 25 Stars (GitHub): 66 Not marked · First seen 2026-10-12	Not listed
Official MCP Registry	Not listed	Listed Version: 0.42.0 Downloads/month (npm): 34 553 Downloads/week (npm): 6 200 Forks (GitHub): 51 Stars (GitHub): 44 Not marked · First seen 2026-10-11
Docker MCP Catalog	Not listed	Listed Version: sha256:8a64acae01b6 Forks (GitHub): 51 Pulls (Docker Hub): 14 724 Stars (Docker Hub): 0 Stars (GitHub): 44 Not marked · First seen 2026-10-11

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

super-claude-for-sap vs SmartBear MCP
Fact	super-claude-for-sap	SmartBear MCP
Marketplaces that list it (differs)	1 (worse)	2 (better)
Stars (GitHub) (differs)	66 (better)	44 (worse)
Pulls (Docker Hub) (differs)	No figure on Docker Hub	14 724
Forks (GitHub) (differs)	25 (worse)	51 (better)
Last release	Not published	Not published
Where it runs (differs)	Installs as a plugin bundle	Remote server or your machine
Transport (differs)	Not stated	Streamable HTTP, stdio
Tools it declares (differs)	Not published	160
Environment variables it asks for (differs)	2, secrets among them: 0	17, secrets among them: 10
Hooks it runs (differs)	25	Not published
Parts of the bundle (differs)	55	Not a bundle
Licence	MIT	MIT
Repository (differs)	github.com/babamba2/superclaude-for-sap	github.com/smartbear/smartbear-mcp
Changes in the last 7 days	0	0
First seen (differs)	2026-10-12	2026-10-11
Endpoint at the last check (differs)	no remote endpoint we check	Answered with HTTP 400 (4 days 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

super-claude-for-sap

In its own words, on Claude Code: claude-plugins-community:

ABAP Class Creation & Unit Testing Debugging & Root Cause Analysis SPRO Configuration Reference Cross-Module Integration Analysis

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

super-claude-for-sap As a Claude Code plugin

Claude Code

/plugin marketplace add anthropics/claude-plugins-community
/plugin install super-claude-for-sap@claude-community

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 super-claude-for-sap publish no list of tools, so we do not compare tools.

Settings each asks for

Only super-claude-for-sap asks for

CLAUDE_PLUGIN_ROOT
SC4SAP_MCP_AUTOBUILD

Only SmartBear MCP asks for

API_HUB_API_KEY (secret)
BEARQ_API_BASE_URL
BEARQ_API_TOKEN (secret)
BUGSNAG_AUTH_TOKEN (secret)
BUGSNAG_ENDPOINT
BUGSNAG_PROJECT_API_KEY
PACT_BROKER_BASE_URL
PACT_BROKER_PASSWORD (secret)
PACT_BROKER_TOKEN (secret)
PACT_BROKER_USERNAME
QTM4J_API_KEY (secret)
QTM4J_AUTOMATION_API_KEY (secret)

Show the remaining 7

QTM4J_BASE_URL
REFLECT_API_TOKEN (secret)
SWAGGER_API_KEY (secret)
SWAGGER_FUNCTIONAL_TESTING_API_TOKEN (secret)
SWAGGER_FUNCTIONAL_TESTING_BASE_PATH
ZEPHYR_API_TOKEN (secret)
ZEPHYR_BASE_URL

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

What it can do: super-claude-for-sap · What it can do: SmartBear MCP · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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 2026-10-28. We publish no contact details for plugin publishers.