Ext Ops Panel
Open dashboard
Comparison

io.github.SuperAgentic/spines vs LoreDocs

io.github.SuperAgentic/spines is an MCP server published by SuperAgentic. Marketplaces we read that list it: 1 (Official MCP Registry). LoreDocs is an MCP server published by labyrinth-analytics. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-17. 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
Marketplaceio.github.SuperAgentic/spinesLoreDocs
Official MCP Registry Listed
Version: 1.1.0
Downloads/month (npm): 118
Downloads/week (npm): 16
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.1.28
Downloads/month (PyPI): 581
Downloads/week (PyPI): 163
Forks (GitHub): 0
Stars (GitHub): 4
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 0.1.19
Forks (GitHub): 0
Stars (GitHub): 4
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

io.github.SuperAgentic/spines vs LoreDocs
Factio.github.SuperAgentic/spinesLoreDocs
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)4 (better)
Forks (GitHub)00
Last release (differs)2026-10-14Not published
Where it runs (differs)On your machine (@spines/mcp-server)On your machine (loredocs)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for1, secrets among them: 11, secrets among them: 1
Parts of the bundle (differs)Not a bundle3
Licence (differs)Not statedBSL-1.1
Repository (differs)github.com/getspines/mcp-servergithub.com/labyrinth-analytics/loredocs
Changes in the last 7 days (differs)20
First seen2026-10-112026-10-11

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

io.github.SuperAgentic/spines

In its own words, on Official MCP Registry:

Access book collections, reading lists, and bookshelf recognition from AI assistants.

LoreDocs

In its own words, on Official MCP Registry:

Local-first knowledge vaults for project docs and specs. Tagged, versioned, full-text searchable.

How to run each

io.github.SuperAgentic/spines As a local MCP server: npm package

Claude Code
claude mcp add --env "SPINES_API_KEY=<YOUR_SPINES_API_KEY>" --transport stdio spines -- npx -y @spines/mcp-server

Requires: SPINES_API_KEY (secret)

LoreDocs As a local MCP server: PyPI package

Claude Code
claude mcp add --env "LOREDOCS_PRO=<YOUR_LOREDOCS_PRO>" --transport stdio loredocs -- uvx loredocs

Requires: LOREDOCS_PRO (secret)

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

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only io.github.SuperAgentic/spines asks for

  • SPINES_API_KEY (secret)

Only LoreDocs asks for

  • LOREDOCS_PRO (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: io.github.SuperAgentic/spines · What it can do: LoreDocs · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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