buildin vs Living Docs
buildin is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑23.
buildin is a plugin bundle for AI coding tools published by AI Hub Contributors. 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-28. 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 dodobrands/ai-hub | Removed on 2026-10-23 Version: 2.5.1 Forks (GitHub): 8 Stars (GitHub): 8 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 | buildinno longer listed · | Living Docs |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 8 | 0 |
| Forks (GitHub) (differs) | 8 | 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 |
| Parts of the bundle (differs) | 3 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/dodobrands/ai-hub | github.com/s2bomb/living-docs-connect |
| Changes in the last 7 days (differs) | 3 | 0 |
| First seen (differs) | 2026-10-16 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-24 |
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 buildin
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Read and update your team's Folio wiki from Claude Code: the Folio MCP server and a skill that tells the agent how to work with pages, tables and boards.
-
Generate and maintain OpenWiki-format repo docs using Claude Code's own inference — no separate API key.
-
Write, organize and publish documentation sites, help centers and SOPs on OpenDocs.cloud.
-
confluence-hardened
Search and manage Confluence pages and spaces using confluence-cli — read docs, create pages, and navigate spaces.
-
AutEng Docs — Agent Document Workspace & Publishing
Agent document workspace with wallet auth. Create, update and share markdown docs. By AutEng.ai
-
📚 FAOS Technical Writer — Technical Documentation Specialist + Knowledge Curator
What each says it does
buildin
Buildin.ai wiki page management — create and update documentation pages; comment threads: comment, reply, resolve, mention, rollback
Living Docs
Create and improve live, shared interactive documents with your agent.
How to run each
buildin
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: buildin · 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.