engineering-docs vs Living Docs
engineering-docs is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑21.
engineering-docs is a plugin bundle for AI coding tools published by Fattain Naime. No marketplace we read lists it any more. Living Docs is an MCP server published by s2bomb. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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 |  Living Docs | |
|---|---|---|
| Community marketplace fattain-naime/engineering-docs | Removed on 2026-10-21 Version: 1.2.2 Forks (GitHub): 2 Stars (GitHub): 6 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.4.0 Forks (GitHub): 0 Stars (GitHub): 0 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 | engineering-docsno longer listed · | Living Docs |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 6 | 0 |
| Forks (GitHub) (differs) | 2 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (living-docs-workspace.vercel.app/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 28 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/fattain-naime/engineering-docs | github.com/s2bomb/living-docs-connect |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-18 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 days ago, requires a key |
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 engineering-docs
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Skills for authoring and reviewing technical documents: ADRs, CLAUDE.md, project docs, and independent document review with structured evaluation.
-
Documentation conventions plus a learn-with-docs knowledge base for solved problems
-
document-skills
Collection of document and configuration skills including human-readable and design-system documentation, ISO 24495-1 plain-language writing, skill creation and evaluation…
-
📚 FAOS Technical Writer — Technical Documentation Specialist + Knowledge Curator
-
技術ドキュメントの作成・レビュー用 Claude Code プラグイン（日本語版）。
-
Engineering & tech skills: Code Review Checklist, Incident Postmortem, API Docs Writer, Architecture Decision Record, Debugging Log Analyser, PR Description Writer, System Design…
What each says it does
engineering-docs
22 engineering documentation skills covering the complete software lifecycle.
Living Docs
Create and improve live, shared interactive documents with your agent.
How to run each
engineering-docs
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Living Docs As a remote MCP server
claude mcp add --transport http living-docs https://living-docs-workspace.vercel.app/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Living Docs has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: engineering-docs · What it can do: Living Docs · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.