speckit-generator vs SmartBear MCP
speckit-generator is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑28.
speckit-generator is a plugin bundle for AI coding tools published by Claude Code Skills. No marketplace we read lists it any more. SmartBear MCP is an MCP server published by smartbear.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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
| Marketplace |  SmartBear MCP | |
|---|---|---|
| Community marketplace ddunnock/claude-plugins | Removed on 2026-10-28 Version: 2.1.1 Forks (GitHub): 7 Stars (GitHub): 14 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.43.0 Downloads/month (npm): 34 553 Downloads/week (npm): 6 200 Forks (GitHub): 50 Stars (GitHub): 44 Not marked · First seen |
| Docker MCP Catalog | Not listed | Removed on 2026-11-07 Version: sha256:8a64acae01b6 Forks (GitHub): 50 Pulls (Docker Hub): 15 119 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
| Fact | speckit-generatorno longer listed · | SmartBear MCP |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 14 | 44 |
| Forks (GitHub) (differs) | 7 | 50 |
| Last release (differs) | Not published | 2026-11-03 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (bugsnag.mcp.smartbear.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 17, secrets among them: 10 |
| Hooks it runs (differs) | 5 | Not published |
| Parts of the bundle (differs) | 17 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/ddunnock/claude-plugins | github.com/smartbear/smartbear-mcp |
| Changes in the last 7 days (differs) | 0 | 3 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 42 h ago returned HTTP 400 |
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 speckit-generator
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Explore directions through research-led brainstorming, write comprehensive specs, and implement them with risk-first subagent workflows and live verification
-
Specification-driven development workflow: setup → specify → plan → tasks → implement
-
Spec-driven development engine: turns feature specs into working code through structured requirements, wave-based parallel agent execution, and automated quality gates.
-
Spec-driven development methodology with skills for requirements, design, tasks, AI prompting, QA, and troubleshooting
-
GitHub Spec-Kit integration for Specification-Driven Development - define WHAT and HOW before coding
-
Specification Driven Development workflow commands and agents, based on Github Spec Kit and OpenSpec. Uses specialized agents for effective context management and quality review.
What each says it does
speckit-generator
Specification and task management with PLANS taxonomy, ADR-style decisions, SMART acceptance criteria, SEAMS clarification, anti-pattern detection (50 patterns), 4-level verification (stub detection + wiring checks), execution orchestration (deviation rules, checkpoint taxonomy, auth gates, session continuity), tech-specific designer agents, git checkpoints, and session-memory hooks. Outputs to speckit/ directory.
SmartBear MCP
MCP server for AI access to SmartBear tools, including BugSnag, Reflect, Swagger, PactFlow, QTM4J.
How to run each
speckit-generator
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 mcp add --transport http smartbear-mcp https://bugsnag.mcp.smartbear.com/mcpRequires: 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
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of speckit-generator publish no settings it asks for, so we do not compare settings.
What it can do: speckit-generator · 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.