Sequential Thinking (Reference) vs spec-interview
spec-interview is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑29.
Sequential Thinking (Reference) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). spec-interview is a plugin bundle for AI coding tools published by Leandro Zubrezki. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-29. 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 | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:cd3174b2ecf3 Forks (GitHub): 11 888 Pulls (Docker Hub): 430 847 Stars (Docker Hub): 30 Stars (GitHub): 91 682 Not marked · First seen |
Not listed |
| Community marketplace leandroz/claude-plugins | Not listed | Removed on 2026-10-29 Version: 1.1.1 Forks (GitHub): 0 Stars (GitHub): 15 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 | Sequential Thinking (Reference) | spec-interviewno longer listed · |
|---|---|---|
| Marketplaces that list it (differs) | 1 | 0 |
| Stars (GitHub) (differs) | 91 682 | 15 |
| Pulls (Docker Hub) (differs) | 430 847 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 11 888 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/sequentialthinking) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 1 | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | Not a bundle | 1 |
| Licence (differs) | NOASSERTION | MIT |
| Repository (differs) | github.com/modelcontextprotocol/servers | github.com/leandroz/claude-plugins |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen (differs) | 2026-10-11 | 2026-10-26 |
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 spec-interview
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
An expert-guided skill for creating layered software specification documents for greenfield projects. Produces Vision, Business Requirements, Software Requirements, Architecture…
-
Interview command for fleshing out big feature plans and specifications
-
Spec-driven development methodology with skills for requirements, design, tasks, AI prompting, QA, and troubleshooting
-
Specification review: analyze specs for gaps, inconsistencies, and scope estimation
-
Drive work from written specifications: author and update spec files, derive GitHub issues and epics, break down features and test plans, write product requirements, and refine a…
-
Create and review technical specifications
What each says it does
Sequential Thinking (Reference)
Dynamic and reflective problem-solving through thought sequences.
spec-interview
Multi-round interview to refine a rough SPEC.md into a complete, implementation-ready specification with tasks
How to run each
Sequential Thinking (Reference) As a local MCP server: Docker image
claude mcp add --transport stdio sequentialthinking -- docker run -i --rm mcp/sequentialthinking
spec-interview
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of spec-interview publish no list of tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Sequential Thinking (Reference) · What it can do: spec-interview · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.