Ext Ops Panel
Open dashboard
Comparison

Sequential Thinking (Reference) vs harness-designing-plugin

Sequential Thinking (Reference) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). harness-designing-plugin is a plugin bundle for AI coding tools published by BilLogic. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-12. 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
MarketplaceSequential Thinking (Reference)harness-designing-plugin
Docker MCP Catalog Listed
Version: sha256:cd3174b2ecf3
Forks (GitHub): 11 780
Pulls (Docker Hub): 420 186
Stars (Docker Hub): 30
Stars (GitHub): 91 180
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 3.0.0
Forks (GitHub): 0
Stars (GitHub): 5
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

Sequential Thinking (Reference) vs harness-designing-plugin
FactSequential Thinking (Reference)harness-designing-plugin
Marketplaces that list it11
Stars (GitHub) (differs)91 180 (better)5 (worse)
Pulls (Docker Hub) (differs)420 186No figure on Docker Hub
Forks (GitHub) (differs)11 780 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/sequentialthinking)Remote server (mcp.context7.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)1Not published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle5
Licence (differs)NOASSERTIONMIT
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/billogic/harness-designing-plugin
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

Sequential Thinking (Reference)

In its own words, on Docker MCP Catalog:

Dynamic and reflective problem-solving through thought sequences.

harness-designing-plugin

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

Harness Designing Plugin helps design teams turn their scattered AI setup — Notion prompts, Figma comments, AGENTS.md rules, chat histories — into a five-layer design harness that compounds across sessions and rotations. Four skills walk you through the assembly: • /hd:learn — Q&A about the five-layer concept (Context Engineering, Skill Curation, Workflow Orchestration, Rubric Setting, Knowledge Compounding) • /hd:setup — detects existing harness artifacts, pre-analyzes all five layers in parallel (5× harness-auditor + rubric-recommender), then walks you through link / critique / scaffold / skip per layer • /hd:maintain — captures lessons and promotes them to team rules in AGENTS.md with SHA-256 plan-hash proof-of-consent • /hd:review — audits harness health in a 2-batch parallel dispatch (5 layer-specialist agents + 2–3 context agents); critiques harness artifacts against quality rubrics Ships 9 sub-agents and 14 starter rubrics (distilled from pbakaus/impeccable, Nielsen's 10 heuristics, Material 3, Fluent

How to run each

Sequential Thinking (Reference) As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio sequentialthinking -- docker run -i --rm mcp/sequentialthinking

harness-designing-plugin

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 harness-designing-plugin 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: harness-designing-plugin · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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