Atlas Docs vs glossary-builder
glossary-builder is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
Atlas Docs is an MCP server published by CartographAI. Marketplaces we read that list it: 1 (Docker MCP Catalog). glossary-builder is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-24. 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 |  Atlas Docs | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:4d235adb7498 Forks (GitHub): 5 Pulls (Docker Hub): 24 340 Stars (Docker Hub): 2 Stars (GitHub): 36 Not marked · First seen |
Not listed |
| Community marketplace barnburner121/claude-plugin-marketplace | Not listed | Removed on 2026-10-18 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 3 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 | Atlas Docs | glossary-builderno longer listed · |
|---|---|---|
| Marketplaces that list it (differs) | 1 | 0 |
| Stars (GitHub) (differs) | 36 | 3 |
| Pulls (Docker Hub) (differs) | 24 340 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 5 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/atlas-docs) | On your machine (@barnburner121/plugin-hub-mcp) |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 5 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | Not published |
| Parts of the bundle (differs) | Not a bundle | 2 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/cartographai/atlas-docs-mcp | github.com/barnburner121/claude-plugin-marketplace |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-14 |
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.
-
Write and review software documentation in Simplified Technical English. Includes a skill, three agents, four commands, and a linter with 19 rules.
-
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
What each says it does
Atlas Docs
Provide LLMs hosted, clean markdown documentation of libraries and frameworks.
glossary-builder
Extract domain terms and generate glossary
How to run each
Atlas Docs As a local MCP server: Docker image
claude mcp add --transport stdio atlas-docs -- docker run -i --rm mcp/atlas-docsglossary-builder
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of glossary-builder publish no list of tools, so we do not compare tools.
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: Atlas Docs · What it can do: glossary-builder · 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.