Ext Ops Panel
Open dashboard
Comparison

io.github.Evanciel/stellavault vs LoreDocs

io.github.Evanciel/stellavault is an MCP server published by Evanciel. 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-24. 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.Evanciel/stellavaultLoreDocs
Official MCP Registry Listed
Version: 0.9.0
Downloads/month (npm): 301
Downloads/week (npm): 21
Forks (GitHub): 2
Stars (GitHub): 5
Not marked · First seen
Listed
Version: 0.1.28
Downloads/month (PyPI): 581
Downloads/week (PyPI): 291
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.Evanciel/stellavault vs LoreDocs
Factio.github.Evanciel/stellavaultLoreDocs
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)5 (better)4 (worse)
Forks (GitHub) (differs)2 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (stellavault)On your machine (loredocs)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 01, secrets among them: 1
Parts of the bundle (differs)Not a bundle3
Licence (differs)MITBSL-1.1
Repository (differs)github.com/evanciel/stellavaultgithub.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.Evanciel/stellavault

In its own words, on Official MCP Registry:

Local-first MCP server: Claude searches, asks & drafts from your Obsidian vault. 21 tools, no keys.

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.Evanciel/stellavault As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio stellavault -- npx -y stellavault serve

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.Evanciel/stellavault asks for

  • STELLAVAULT_DB_PATH

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.Evanciel/stellavault · 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 public marketplace files in GitHub repositories of their authors. 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