Ext Ops Panel
Open dashboard
Comparison

LoreConvo vs Engram

LoreConvo is an MCP server published by labyrinth-analytics. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). Engram is an MCP server published by engram.tools. 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

Where each is published
MarketplaceLoreConvoEngram
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: 0.4.8
Downloads/month (npm): 580
Downloads/week (npm): 416
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

LoreConvo vs Engram
FactLoreConvoEngram
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)11No figure on GitHub
Forks (GitHub) (differs)1No figure on GitHub
Last release (differs)Not published2026-10-16
Where it runs (differs)On your machine (loreconvo)Remote server (api.engram.tools/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 12, secrets among them: 1
Hooks it runs (differs)4Not published
Parts of the bundle (differs)7Not a bundle
Licence (differs)BSL-1.1Not stated
Repository (differs)github.com/labyrinth-analytics/loreconvoNot stated
Changes in the last 7 days (differs)01
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 h ago, requires a key

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

In its own words, on Official MCP Registry:

Local-first persistent session memory for Claude Code and other agents. SQLite + FTS5, no cloud.

Engram

In its own words, on Official MCP Registry:

Memory for AI agent teams across tools, sessions, repositories, and teammates.

How to run each

LoreConvo As a local MCP server: PyPI package

Claude Code
claude mcp add --env "LORECONVO_PRO=<YOUR_LORECONVO_PRO>" --transport stdio loreconvo -- uvx loreconvo

Requires: LORECONVO_PRO (secret)

Engram As a remote MCP server

Claude Code
claude mcp add --transport http engram https://api.engram.tools/mcp

Requires: ENGRAM_API_KEY (secret), ENGRAM_API_URL

Commands built only from what the marketplaces declare; the full set for every client is on each card.

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

Only LoreConvo asks for

  • LORECONVO_PRO (secret)

Only Engram asks for

  • ENGRAM_API_KEY (secret)
  • ENGRAM_API_URL

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

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

Where the data comes from: how the catalog is built