Ext Ops Panel
Open dashboard
Comparison

recall vs LLMemory

recall is a plugin bundle for AI coding tools published by bledden. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). LLMemory is an MCP server published by meir-may. 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
MarketplacerecallLLMemory
Claude Code: claude-plugins-community Listed
Version: 2.2.3
Forks (GitHub): 1
Stars (GitHub): 23
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
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

recall vs LLMemory
FactrecallLLMemory
Marketplaces that list it11
Stars (GitHub) (differs)23 (better)0 (worse)
Forks (GitHub) (differs)1 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.llmemory.xyz/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)4Not published
Parts of the bundle (differs)6Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/bledden/claude-recall-plugingithub.com/meir-may/llmemory-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 days 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

recall

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

Persistent conversation recall for Claude Code. Indexes every exchange into a local SQLite database so you can search, browse, and recover context at any time. Survives /clear commands and context compaction. Search across all sessions in a project or globally across every project. Auto-tags technical terms for discovery. Shares findings between parallel sessions via opt-in highlight connections. Includes a PostCompact nudge that automatically re-orients Claude after context loss. Optional proactive skill teaches Claude to detect context loss and suggest recall commands. Zero external dependencies, pure Python stdlib with FTS5 full-text search and WAL mode for concurrent session safety.

LLMemory

In its own words, on Official MCP Registry:

Search your AI chat history (ChatGPT, Claude, Codex) from any MCP client. Remote, private, read-only

How to run each

recall As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install recall@claude-community

LLMemory As a remote MCP server

Claude Code
claude mcp add --transport http llmemory https://mcp.llmemory.xyz/mcp

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

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

Neither one's marketplaces publish the settings it asks for.

What it can do: recall · What it can do: LLMemory · 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