LoreConvo vs r3
LoreConvo is an MCP server published by labyrinth-analytics. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). r3 is an MCP server published by n3wth. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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
| Marketplace |  LoreConvo |  r3 |
|---|---|---|
| Official MCP Registry | Listed Version: 0.10.12 Downloads/month (PyPI): 902 Downloads/week (PyPI): 177 Forks (GitHub): 1 Stars (GitHub): 11 Not marked · First seen |
Listed Version: 1.3.2 Downloads/month (npm): 209 Downloads/week (npm): 32 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
| Claude Code: claude-plugins-community | Listed Version: 0.9.0 Forks (GitHub): 1 Stars (GitHub): 11 Not marked · First seen |
Not listed |
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 | LoreConvo | r3 |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 11 (better) | 2 (worse) |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (loreconvo) | On your machine (@n3wth/r3) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 2, secrets among them: 1 |
| Hooks it runs (differs) | 4 | Not published |
| Parts of the bundle (differs) | 7 | Not a bundle |
| Licence (differs) | BSL-1.1 | Not stated |
| Repository (differs) | github.com/labyrinth-analytics/loreconvo | github.com/n3wth/r3 |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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
LoreConvo
Local-first persistent session memory for Claude Code and other agents. SQLite + FTS5, no cloud.
r3
Local Redis memory MCP for AI apps with hybrid caching and optional Mem0 cloud backup.
How to run each
LoreConvo As a local MCP server: PyPI package
claude mcp add --env "LORECONVO_PRO=<YOUR_LORECONVO_PRO>" --transport stdio loreconvo -- uvx loreconvoRequires: LORECONVO_PRO (secret)
r3 As a local MCP server: npm package
claude mcp add --env "MEM0_API_KEY=<YOUR_MEM0_API_KEY>" --transport stdio r3 -- npx -y @n3wth/r3Requires: MEM0_API_KEY (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
Only LoreConvo asks for
LORECONVO_PRO (secret)
Only r3 asks for
MEM0_API_KEY (secret)REDIS_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: LoreConvo · What it can do: r3 · Compare two other plugins
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.