Comparison

hub-meta vs LoreDocs

hub-meta is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑23.

hub-meta is a plugin bundle for AI coding tools published by AI Hub Contributors. 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-27. 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

Where each is published
Marketplace	hub-meta	LoreDocs
Community marketplace dodobrands/ai-hub	Removed on 2026-10-23 Version: 1.2.3 Forks (GitHub): 8 Stars (GitHub): 8 Not marked · First seen 2026-10-16	Not listed
Official MCP Registry	Not listed	Listed Version: 0.1.28 Downloads/month (PyPI): 581 Downloads/week (PyPI): 291 Forks (GitHub): 0 Stars (GitHub): 4 Not marked · First seen 2026-10-11
Claude Code: claude-plugins-community	Not listed	Listed Version: 0.1.19 Forks (GitHub): 0 Stars (GitHub): 4 Not marked · First seen 2026-10-11

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

hub-meta vs LoreDocs
Fact	hub-metano longer listed · 2026-10-23	LoreDocs
Marketplaces that list it (differs)	0	2
Stars (GitHub) (differs)	8	4
Forks (GitHub) (differs)	8	0
Last release	Not published	Not published
Where it runs (differs)	Installs as a plugin bundle	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)	4	3
Licence (differs)	Not stated	BSL-1.1
Repository (differs)	github.com/dodobrands/ai-hub	github.com/labyrinth-analytics/loredocs
Changes in the last 7 days (differs)	3	0
First seen (differs)	2026-10-16	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 hub-meta

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

utils

Core AIWG utilities for context regeneration and workspace management.

by AIWG Contributors · Plugin bundle

Listed on: Community GitHub marketplaces · Describes nearly the same job
aria-knowledge

Knowledge management, decision discipline, codebase understanding, plan pre-mortems, and release retrospectives for Claude Code

by Mike Prasad · Plugin bundle

Listed on: Community GitHub marketplaces · Describes nearly the same job
PAPI: Persistent Adaptive Project Intelligence

Adaptive plan/build/review cycles for AI coding assistants, persisted across sessions.

by getpapi · MCP server

Listed on: Official MCP Registry, npm registry (MCP servers), Community GitHub marketplaces · Describes nearly the same job
ai-ready

Analyze any repository and generate AI-ready configuration — AGENTS.md, copilot-instructions.md, CI workflows, issue templates, and more. Mines your PR review patterns and creates…

by johnpapa · Plugin bundle

Listed on: Copilot CLI: github/awesome-copilot, Community GitHub marketplaces · Describes nearly the same job
Umtri

Give your AI agent a persistent map of your project's structure, dependencies, and bugs.

by umtri.io · MCP server

Listed on: Official MCP Registry · Describes nearly the same job
Dev Tools

Dev-tools — scaffold repos, multi-agent QA review, templatize. Session-handover commands and agent moved to claude-hopper in 1.2.0.

by danielrosehill · Plugin bundle

Listed on: Community GitHub marketplaces · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

hub-meta

In its own words, on Community GitHub marketplaces:

AI Hub meta-tools — setup wizard, create new commands, run session retrospectives, update subtree from upstream

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

hub-meta

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 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

The marketplaces of hub-meta publish no settings it asks for, so we do not compare settings.

What it can do: hub-meta · 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 2026-10-27. We publish no contact details for plugin publishers.