Comparison

recallnest vs Perenna

recallnest is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑29.

recallnest is a plugin bundle for AI coding tools published by aliceljy. No marketplace we read lists it any more. Perenna is an MCP server published by scarletkc. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-11-07. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplace	recallnest	Perenna
Community marketplace aliceljy/recallnest	Removed on 2026-10-29 Version: 4.0.0 Forks (GitHub): 4 Stars (GitHub): 15 Not marked · First seen 2026-10-15	Not listed
Official MCP Registry	Not listed	Listed Version: 0.4.1 Downloads/month (PyPI): 248 Downloads/week (PyPI): 29 Forks (GitHub): 2 Stars (GitHub): 60 Not marked · First seen 2026-10-11

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

recallnest vs Perenna
Fact	recallnestno longer listed · 2026-10-29	Perenna
Marketplaces that list it (differs)	0	2
Stars (GitHub) (differs)	15	60
Forks (GitHub) (differs)	4	2
Last release	Not published	Not published
Where it runs (differs)	Installs as a plugin bundle	On your machine (perenna)
Transport (differs)	Not stated	stdio
Tools it declares	Not published	Not published
Environment variables it asks for (differs)	3, secrets among them: 1	4, secrets among them: 2
Parts of the bundle	2	2
Licence (differs)	Not stated	MIT
Repository (differs)	github.com/aliceljy/recallnest	github.com/scarletkc/perenna
Changes in the last 7 days	0	0
First seen (differs)	2026-10-15	2026-10-11

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of recallnest

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

Memex — Local AI Memory

Local AI memory system for Claude Code and Cursor. Remembers your preferences, decisions, and project context across sessions using a Go HTTP service and Qdrant vector database…

by Shvmvrshny · Plugin bundle

Listed on: Claude Code: claude-plugins-community · Describes nearly the same job
loci

Cross-session memory and hybrid RAG over your notes and docs. Local-first, with cited answers.

by IvenKooLab · MCP server

Listed on: Official MCP Registry · Describes nearly the same job
cogvault

Local hybrid-search memory for AI agents over plain Markdown. Multi-tenant, offline, no LLM.

by NBibikov · MCP server

Listed on: Official MCP Registry · Describes nearly the same job
ourmem

Persistent memory for Claude Code — memories survive across sessions, projects, and machines

by ourmem · Plugin bundle

Listed on: Community GitHub marketplaces · Describes nearly the same job
agent-recall

Persistent memory for AI coding agents. SQLite knowledge graph with scoped entities, MCP tools, and LLM-summarized briefings.

by mnardit · Plugin bundle

Listed on: Claude Code: claude-plugins-community · Describes nearly the same job
ensue-memory

Persistent memory layer for AI agents. Store, recall, search, and share memories with semantic search. Triggers on 'remember', 'recall', 'search memories', 'update memory…

by Ensue · Plugin bundle

Listed on: Community GitHub marketplaces · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

recallnest

In its own words, on Community GitHub marketplaces:

Local-first memory system: store, search, and recall context across sessions and terminals. Powered by LanceDB with hybrid retrieval.

Perenna

In its own words, on Official MCP Registry:

A lightweight, Git-backed permanent memory for AI agents.

How to run each

recallnest

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Perenna As a local MCP server: PyPI package

Claude Code

claude mcp add --env "VEXOR_API_KEY=<YOUR_VEXOR_API_KEY>" --env "VEXOR_REMOTE_RERANK_API_KEY=<YOUR_VEXOR_REMOTE_RERANK_API_KEY>" --transport stdio perenna -- uvx perenna mcp

Requires: VEXOR_API_KEY (secret), VEXOR_REMOTE_RERANK_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 recallnest asks for

JINA_API_KEY (secret)
LOCAL_MEMORY_CONFIG
RECALLNEST_MCP_TIER

Only Perenna asks for

PERENNA_GIT_REMOTE
VEXOR_API_KEY (secret)
VEXOR_CONFIG_JSON
VEXOR_REMOTE_RERANK_API_KEY (secret)

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

What it can do: recallnest · What it can do: Perenna · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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 2026-11-07. We publish no contact details for plugin publishers.