pearl-llm-memory vs KEPTA — the memory for AI systems
pearl-llm-memory is a plugin bundle for AI coding tools published by reneemgagnon. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). KEPTA — the memory for AI systems is an MCP server published by DamianTodorovic. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-21. 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 | ||
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: fff8a3e No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 3.4.0 Downloads/month (npm): 5 290 Downloads/week (npm): 210 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 3.4.0 Downloads/month (npm): 5 290 Downloads/week (npm): 210 Forks (GitHub): 0 Stars (GitHub): 2 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 | pearl-llm-memory | KEPTA — the memory for AI systems |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 2 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | Not published | 2026-10-14 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (kepta-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Not stated | BUSL-1.1 |
| Repository (differs) | github.com/reneemgagnon/pearl_llm_memory | github.com/damiantodorovic/kepta |
| 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
pearl-llm-memory
Externalized Cognitive State Transfer PEARL-LLM Memory (.pearl) is a JSON-based file format for storing structured, layered, verifiable context that persists across agent sessions. It gives autonomous agents a durable memory with immutable history, temperature-graded recall, cryptographic chain of custody, and branching decision trails. The format is agent-agnostic. The reference implementation is a zero-dependency Python CLI. Both are open.
KEPTA — the memory for AI systems
Local encrypted memory for AI: hybrid search, 8 MCP tools, one file you own. Free, no cloud.
How to run each
pearl-llm-memory As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install pearl-llm-memory@claude-community
KEPTA — the memory for AI systems As a local MCP server: npm package
claude mcp add --transport stdio kepta -- npx -y kepta-mcp
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
Neither one's marketplaces publish the settings it asks for.
What it can do: pearl-llm-memory · What it can do: KEPTA — the memory for AI systems · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.