glossary-builder vs LoreDocs
glossary-builder is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
glossary-builder is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. 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-30. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  LoreDocs | |
|---|---|---|
| Community marketplace barnburner121/claude-plugin-marketplace | Removed on 2026-10-18 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.32 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
| Fact | glossary-builderno longer listed · | LoreDocs |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 3 | 4 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-29 |
| Where it runs (differs) | On your machine (@barnburner121/plugin-hub-mcp) | On your machine (loredocs) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Parts of the bundle (differs) | 2 | 3 |
| Licence (differs) | MIT | BSL-1.1 |
| Repository (differs) | github.com/barnburner121/claude-plugin-marketplace | github.com/labyrinth-analytics/loredocs |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of glossary-builder
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
agreement io.github.theluckystrike/agreement
Reusable agreement and proposal clauses assembled into a real Word docx, variables filled.
-
Seven plain language skills inspired by the ISO 24495 series, covering prose, code, and a user-invoked text audit.
-
Agents for writing, formatting, and validating documentation and technical content
-
Deterministic prose linter for LLM text — flags AI slop, filler, buzzwords, hedges, clichés.
-
Build dictionaries & glossaries with AI: entries, senses, versions, print PDF, EPUB, web reader, RTL
-
Technical documentation and API documentation expert
What each says it does
glossary-builder
Extract domain terms and generate glossary
LoreDocs
Local-first knowledge vaults for project docs and specs. Tagged, versioned, full-text searchable.
How to run each
glossary-builder
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
LoreDocs As a local MCP server: PyPI package
claude mcp add --env "LOREDOCS_PRO=<YOUR_LOREDOCS_PRO>" --transport stdio loredocs -- uvx loredocsRequires: 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
The marketplaces of glossary-builder publish no settings it asks for, so we do not compare settings.
What it can do: glossary-builder · What it can do: LoreDocs · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.