Ext Ops Panel
Open dashboard
Comparison

mneme vs Perenna

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

mneme is a plugin bundle for AI coding tools published by Onour Impram. 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-10. 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
MarketplacemnemePerenna
Community marketplace onourimpram/mneme Removed on 2026-10-17
Version: 4.1.0
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
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

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

mneme vs Perenna
Factmnemeno longer listed · Perenna
Marketplaces that list it (differs)02
Stars (GitHub) (differs)360
Forks (GitHub) (differs)02
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (perenna)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published4, secrets among them: 2
Hooks it runs (differs)6Not published
Parts of the bundle (differs)122
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/onourimpram/mnemegithub.com/scarletkc/perenna
Changes in the last 7 days00
First seen (differs)2026-10-142026-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 mneme

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

  • remnic

    Persistent long-term memory for Claude Code — wires SessionStart/UserPromptSubmit/PostToolUse hooks, MCP tools, memory skills, and the memory-review agent into a running Remnic…

    by Joshua Warren · Plugin bundle

    Listed on: Community GitHub marketplaces · 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

  • CogniCore

    Automatic local memory across sessions and agents (Claude Code, Codex). No model calls to save.

    by CogniCore · Plugin bundle

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

  • mengram

    Persistent memory for Claude Code that survives /clear, machine switches, and team handoffs. Hosted memory backend with hybrid retrieval (vector + BM25 + RRF), Ebbinghaus temporal…

    by Ali Baizhanov · Plugin bundle

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

  • memora

    Persistent semantic memory for Claude Code — auto-injects relevant context at session start, captures git commits, test results, and research via hooks, and provides 30+ MCP tools…

    by agentic-mcp-tools · Plugin bundle

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

  • 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

Its card, with similar plugins by marketplace

What each says it does

mneme

In its own words, on Community GitHub marketplaces:

Vault-native memory for Claude Code. Markdown is ground truth. Hybrid retrieval, temporal knowledge graph, zero LLM cost on Stop, token-aware adaptive context.

Perenna

In its own words, on Official MCP Registry:

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

How to run each

mneme

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

The marketplaces of mneme publish no settings it asks for, so we do not compare settings.

What it can do: mneme · 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 . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built