Sequential Thinking (Reference) vs builder-loop
builder-loop is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑21.
Sequential Thinking (Reference) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). builder-loop is a plugin bundle for AI coding tools published by Edoardo Spena. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-21. 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 |  Sequential Thinking (Reference) | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:cd3174b2ecf3 Forks (GitHub): 11 830 Pulls (Docker Hub): 425 859 Stars (Docker Hub): 30 Stars (GitHub): 91 419 Not marked · First seen |
Not listed |
| Community marketplace edoardospena/builder-loop | Not listed | Removed on 2026-10-21 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 6 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) | builder-loopno longer listed · |
|---|---|---|
| Marketplaces that list it (differs) | 1 | 0 |
| Stars (GitHub) (differs) | 91 419 | 6 |
| Pulls (Docker Hub) (differs) | 425 859 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 11 830 | 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/edoardospena/builder-loop |
| Changes in the last 7 days (differs) | 0 | 3 |
| First seen (differs) | 2026-10-11 | 2026-10-16 |
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 builder-loop
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Generate ready-to-paste Claude Code prompts with the right agent, orchestration pattern, and safety rails. Orchestrator synthesises patterns from 6 open-source projects into a…
-
Research-backed orchestration for Claude Code. Structured workflow from idea to production with parallel execution, session memory, 70-point validation, autonomous mode, and…
-
Transform Claude Code into an autonomous AI development powerhouse with persistent task management, intelligent agents, and automatic work discovery
-
Output.ai workflow development toolkit for Claude Code. Adds 5 specialist agents (planner, builder, debugger, prompt writer, quality reviewer), 40+ slash-command skills covering…
-
Intelligent prompt optimization using skill-based architecture. Enriches vague prompts with research-based clarifying questions before Claude Code executes them
-
claude-codex-loop orchestrates a structured collaboration loop between Claude Code (designer/reviewer) and OpenAI Codex (auditor/implementer). It runs two stages — design and code…
What each says it does
Sequential Thinking (Reference)
Dynamic and reflective problem-solving through thought sequences.
builder-loop
Make Claude Code prove it finished the job. Runs a substantial coding task as an evidence-driven closed loop and ends with one explicit ship-or-revise decision.
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/sequentialthinkingbuilder-loop
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 builder-loop 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: builder-loop · 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.