Ext Ops Panel
Open dashboard
Comparison

pearl-llm-memory vs io.github.daedalus/mcp-external-memory

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). io.github.daedalus/mcp-external-memory is an MCP server published by daedalus. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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
Marketplacepearl-llm-memoryio.github.daedalus/mcp-external-memory
Claude Code: claude-plugins-community Listed
Version: fff8a3e
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.2
Downloads/month (PyPI): 87
Downloads/week (PyPI): 32
Forks (GitHub): 0
Stars (GitHub): 0
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

pearl-llm-memory vs io.github.daedalus/mcp-external-memory
Factpearl-llm-memoryio.github.daedalus/mcp-external-memory
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (mcp-external-memory)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/reneemgagnon/pearl_llm_memorygithub.com/daedalus/mcp-external-memory
Changes in the last 7 days00
First seen2026-10-112026-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

In its own words, on Claude Code: claude-plugins-community:

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.

io.github.daedalus/mcp-external-memory

In its own words, on Official MCP Registry:

An MCP server that gives LLMs persistent, searchable semantic memory

How to run each

pearl-llm-memory As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install pearl-llm-memory@claude-community

io.github.daedalus/mcp-external-memory As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio mcp-external-memory -- uvx mcp-external-memory

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: io.github.daedalus/mcp-external-memory · 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. 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