Ext Ops Panel
Open dashboard
Comparison

aiqbee vs LoreDocs

aiqbee is a plugin bundle for AI coding tools published by Aiqbee. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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-17. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceaiqbeeLoreDocs
Community marketplace aiqbee/aiqbee-ai Listed
Version: 1.0.1
Forks (GitHub): 2
Stars (GitHub): 7
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.28
Downloads/month (PyPI): 581
Downloads/week (PyPI): 163
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

aiqbee vs LoreDocs
FactaiqbeeLoreDocs
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)7 (better)4 (worse)
Forks (GitHub) (differs)2 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.aiqbee.com/mcp)On your machine (loredocs)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)23
Licence (differs)MITBSL-1.1
Repository (differs)github.com/aiqbee/aiqbee-aigithub.com/labyrinth-analytics/loredocs
Changes in the last 7 days (differs)20
First seen (differs)2026-10-132026-10-11
Endpoint at the last check (differs)Responded 4 days ago, requires a keyno remote endpoint we check

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

aiqbee

In its own words, on Community GitHub marketplaces:

Connect to Aiqbee's AI-powered knowledge graph. Search, create, and link neurons across your architecture, portfolio, and digital strategy brains.

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

aiqbee As a Claude Code plugin

Claude Code
/plugin marketplace add aiqbee/aiqbee-ai
/plugin install aiqbee@aiqbee-marketplace

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.

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

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

What it can do: aiqbee · 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.

Where the data comes from: how the catalog is built