Ext Ops Panel
Open dashboard
Comparison

Itsuki Memory vs Mneme Memory

Itsuki Memory is a plugin bundle for AI coding tools published by Itsuki. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Mneme Memory is an MCP server published by modusensus. 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
MarketplaceItsuki MemoryMneme Memory
Community marketplace 12ziyad/universal-memory-engine Listed
Version: 0.7.0
Forks (GitHub): 4
Stars (GitHub): 13
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.1
Downloads/month (npm): 775
Downloads/week (npm): 58
Forks (GitHub): 22
Stars (GitHub): 170
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

Itsuki Memory vs Mneme Memory
FactItsuki MemoryMneme Memory
Marketplaces that list it11
Stars (GitHub) (differs)13 (worse)170 (better)
Forks (GitHub) (differs)4 (worse)22 (better)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (itsuki.app/mcp)On your machine (mneme-memory)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)3Not published
Parts of the bundle (differs)5Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/12ziyad/universal-memory-enginegithub.com/slow-stack/mneme
Changes in the last 7 days00
First seen (differs)2026-10-152026-10-11
Endpoint at the last check (differs)Responded 2 days ago, requires a keyno remote endpoint we check

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

Itsuki Memory

In its own words, on Community GitHub marketplaces:

Persistent memory for Claude Code: save durable facts and decisions, recall them in any future session. Receipts for every write; your rules decide what is remembered.

Mneme Memory

In its own words, on Official MCP Registry:

Cross-session memory for AI coding agents via six tools; local-first SQLite store.

How to run each

Itsuki Memory As a Claude Code plugin

Claude Code
/plugin marketplace add 12ziyad/universal-memory-engine
/plugin install itsuki@itsuki-plugins

Mneme Memory As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio mneme-memory -- npx -y mneme-memory

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

Only Itsuki Memory 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: Itsuki Memory · What it can do: Mneme Memory · 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