Ext Ops Panel
Open dashboard
Comparison

DeepWiki vs SpecStory Lore

DeepWiki is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). SpecStory Lore is a plugin bundle for AI coding tools published by SpecStory. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-11-08. 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
MarketplaceDeepWikiSpecStory Lore
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Community marketplace specstoryai/getspecstory Not listed Listed
Version: 3.9.0
Forks (GitHub): 92
Stars (GitHub): 1 371
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

DeepWiki vs SpecStory Lore
FactDeepWikiSpecStory Lore
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub1 371
Forks (GitHub) (differs)No figure on GitHub92
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.deepwiki.com/mcp)Installs as a plugin bundle
Transport (differs)Streamable HTTPNot stated
Tools it declares (differs)3Not published
Environment variables it asks forNot publishedNot published
LicenceApache-2.0Apache-2.0
Repository (differs)Not statedgithub.com/specstoryai/getspecstory
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-11-06
Endpoint at the last check (differs)Status out of date: last check 39 h ago returned HTTP 405no remote endpoint we check

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

DeepWiki

In its own words, on Docker MCP Catalog:

Tools for fetching and asking questions about GitHub repositories.

SpecStory Lore

In its own words, on Community GitHub marketplaces:

Mine your SpecStory coding histories into a persistent corpus and forge your repeated workflows into installable agent skills.

How to run each

DeepWiki As a remote MCP server

Claude Code
claude mcp add --transport http deepwiki https://mcp.deepwiki.com/mcp

SpecStory Lore As a Claude Code plugin

Claude Code
/plugin marketplace add specstoryai/getspecstory
/plugin install lore@specstory

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

Only DeepWiki has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of SpecStory Lore 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: DeepWiki · What it can do: SpecStory Lore · 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