Ext Ops Panel
Open dashboard
Comparison

mem0 vs MCP AutoMem

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

mem0 is a plugin bundle for AI coding tools published by Mem0. No marketplace we read lists it any more. MCP AutoMem is an MCP server published by verygoodplugins. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-11-05. 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
Marketplacemem0MCP AutoMem
Community marketplace abidur-rahman-01/tafm Removed on 2026-10-15
Version: 0.2.12
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.10.0
Downloads/month (npm): 1 045
Downloads/week (npm): 402
Forks (GitHub): 15
Stars (GitHub): 67
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

mem0 vs MCP AutoMem
Factmem0no longer listed · MCP AutoMem
Marketplaces that list it (differs)02
Stars (GitHub) (differs)067
Forks (GitHub) (differs)015
Last release (differs)Not published2026-11-05
Where it runs (differs)Remote server (mcp.mem0.ai/mcp)On your machine (@verygoodplugins/mcp-automem)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)112
Parts of the bundle (differs)248
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/abidur-rahman-01/tafmgithub.com/verygoodplugins/mcp-automem
Changes in the last 7 days (differs)04
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 mem0

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

  • 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

  • engram io.github.tstockham96/engram

    Intelligent agent memory with automatic extraction, consolidation, and bi-temporal recall.

    by tstockham96 · MCP server

    Listed on: Official MCP Registry, Claude Code: claude-plugins-community · Describes nearly the same job

  • Mnemoverse Memory

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

    by mnemoverse · MCP server

    Listed on: Official MCP Registry, npm registry (MCP servers) · Describes nearly the same job

  • mem0

    Connect Mem0 to Claude to give your agent persistent memory across sessions. Claude can store user preferences, project context, and conversation history, then search, update, or…

    by mem0ai · Plugin bundle

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

  • MemoCat — Shared AI Memory

    One shared, persistent memory across AI agents and systems, with semantic recall and live updates.

    by MontyGovernance · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • mcp-server in.creo-memories/mcp-server

    Memory system for AI agents with semantic search. Store and recall memories with ease.

    by creo-memories.in · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

mem0

In its own words, on Community GitHub marketplaces:

Mem0 memory layer for AI applications. Add persistent memory, personalization, and semantic search to Claude workflows.

MCP AutoMem

In its own words, on Official MCP Registry:

Graph-vector memory for AI assistants using FalkorDB and Qdrant

How to run each

mem0

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

MCP AutoMem As a Claude Code plugin

Claude Code
/plugin marketplace add verygoodplugins/mcp-automem
/plugin install automem@verygoodplugins-mcp-automem

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: mem0 · What it can do: MCP AutoMem · 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