Ext Ops Panel
Open dashboard
Comparison

mneme vs total-recall

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. total-recall is a plugin bundle for AI coding tools published by strvmarv. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-21. 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
Marketplacemnemetotal-recall
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
Claude Code: claude-plugins-community Not listed Listed
Version: 4.0.4
Forks (GitHub): 5
Stars (GitHub): 15
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 total-recall
Factmnemeno longer listed · total-recall
Marketplaces that list it (differs)01
Stars (GitHub) (differs)315
Forks (GitHub) (differs)05
Last releaseNot publishedNot published
Where it runsInstalls as a plugin bundleInstalls as a plugin bundle
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)63
Parts of the bundle (differs)127
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/onourimpram/mnemegithub.com/strvmarv/total-recall
Changes in the last 7 days (differs)20
First seen (differs)2026-10-142026-10-12

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.

  • Builderforce Memory

    Token-saving persistent memory for AI agents: recall durable facts instead of re-reading files.

    by SeanHogg · MCP server

    Listed on: Official MCP Registry · 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

  • 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

  • claude-memory

    A Claude Code plugin that adds structured, categorized memory to your projects.

    by tars23364-bit · Plugin bundle

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

  • membase

    Membase connects Claude Code to Membase Cloud, giving Claude persistent memory and wiki workflows across coding sessions. It can recall relevant prior context before prompts, save…

    by aristoapp · Plugin bundle

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

  • synaptic

    Persistent local memory for Claude Code — cross-session context, semantic search, zero cloud

    by HYPERLYNQ · 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.

total-recall

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

Coding Agents forget everything when a session ends. total-recall fixes that: a shared memory layer that persists across sessions, tools, and devices. Memory is organized into three tiers (Hot / Warm / Cold) with a 4,000-token budget enforced automatically — so Claude gets relevant context injected at session start without carrying stale noise. Semantic search (all-MiniLM-L6-v2 embeddings, offline) retrieves the right memories on demand. A knowledge base lets you ingest READMEs, API docs, and architecture notes that are retrieved semantically when relevant. An eval framework lets you measure retrieval quality, run benchmarks, and compare config changes — so you know memory is actually helping. All state is local: SQLite + ONNX embeddings, no external services, no API keys required. Works across Claude Code, Copilot CLI, Cursor, Cline, and OpenCode — existing memories auto-import on first run.

How to run each

mneme

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

total-recall As a Claude Code plugin

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

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: mneme · What it can do: total-recall · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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