Ext Ops Panel
Open dashboard
Comparison

Sequential Thinking (Reference) vs Logos — continuity across agents

Sequential Thinking (Reference) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). Logos — continuity across agents is a plugin bundle for AI coding tools published by Coder8124. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-15. 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)Logos — continuity across agents
Docker MCP Catalog Listed
Version: sha256:cd3174b2ecf3
Forks (GitHub): 11 790
Pulls (Docker Hub): 422 092
Stars (Docker Hub): 30
Stars (GitHub): 91 268
Not marked · First seen
Not listed
Community marketplace coder8124/logos Not listed Listed
Version: 0.5.3
No figure published
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 Logos — continuity across agents
FactSequential Thinking (Reference)Logos — continuity across agents
Marketplaces that list it11
Stars (GitHub) (differs)91 268No figure on GitHub
Pulls (Docker Hub) (differs)422 092No figure on Docker Hub
Forks (GitHub) (differs)11 790No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/sequentialthinking)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)1Not published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)Not published8
Parts of the bundle (differs)Not a bundle12
Licence (differs)NOASSERTIONApache-2.0
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/coder8124/logos
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-15

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.

Logos — continuity across agents

In its own words, on Community GitHub marketplaces:

Checkpoint and resume work across Claude Code, Cursor and Codex. Records what was ruled out so the next agent does not repeat it. Local-first: your memory is markdown on your disk.

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

Logos — continuity across agents As a Claude Code plugin

Claude Code
/plugin marketplace add coder8124/logos
/plugin install logos@logos

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of Logos — continuity across agents 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: Logos — continuity across agents · 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.

Where the data comes from: how the catalog is built