Ext Ops Panel
Open dashboard
Comparison

mem-forever vs Mnemoverse Memory

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). Mnemoverse Memory is an MCP server published by mnemoverse. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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-foreverMnemoverse Memory
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.15.3
Downloads/month (npm): 3 918
Downloads/week (npm): 516
Forks (GitHub): 5
Stars (GitHub): 27
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 Mnemoverse Memory
Factmem-foreverMnemoverse Memory
Marketplaces that list it11
Stars (GitHub) (differs)20 (worse)27 (better)
Forks (GitHub) (differs)12 (better)5 (worse)
Last release (differs)Not published2026-10-18
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.mnemoverse.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
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/mnemoverse/mcp-memory-server
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 26 h ago, requires a key

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.

Mnemoverse Memory

In its own words, on Official MCP Registry:

Hosted agent memory that learns from outcomes, with shared rooms. No key: mcp.mnemoverse.com/mcp

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

Mnemoverse Memory As a remote MCP server

Claude Code
claude mcp add --transport http mcp-memory-server https://mcp.mnemoverse.com/mcp

Requires: MNEMOVERSE_API_KEY (secret)

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

Only Mnemoverse 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

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

What it can do: mem-forever · What it can do: Mnemoverse Memory · 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