Ext Ops Panel
Open dashboard
Comparison

mem-forever vs ASR Memory (에사 AI) — Shared memory for AI tools

mem-forever is a plugin bundle for AI coding tools published by ilang-ai. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). ASR Memory (에사 AI) — Shared memory for AI tools is an MCP server published by asrmemory.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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
Marketplacemem-foreverASR Memory (에사 AI) — Shared memory for AI tools
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 12
Stars (GitHub): 20
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.3.2
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

mem-forever vs ASR Memory (에사 AI) — Shared memory for AI tools
Factmem-foreverASR Memory (에사 AI) — Shared memory for AI tools
Marketplaces that list it11
Stars (GitHub) (differs)20 (better)0 (worse)
Forks (GitHub) (differs)12 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (asrmemory.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)3Not published
Parts of the bundle (differs)4Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/ilang-ai/mem-forevergithub.com/xjoanet/asr-memory-docs
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 5 days ago

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

mem-forever

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

Every AI tool forgets you. This one doesn't. Ever. Auto-saves your preferences, decisions, and lessons to .ilang/ — survives every session, every tool, every migration.

ASR Memory (에사 AI) — Shared memory for AI tools

In its own words, on Official MCP Registry:

Shared memory for AI tools: save once, recall word for word from Claude, ChatGPT, Codex or Gemini.

How to run each

mem-forever As a Claude Code plugin

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

ASR Memory (에사 AI) — Shared memory for AI tools As a remote MCP server

Claude Code
claude mcp add --transport http asr https://asrmemory.com/mcp

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

Only ASR Memory (에사 AI) — Shared memory for AI tools 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: mem-forever · What it can do: ASR Memory (에사 AI) — Shared memory for AI tools · 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