Ext Ops Panel
Open dashboard
Comparison

amem vs MemoCat — Shared AI Memory

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

amem is a plugin bundle for AI coding tools published by Aman Asmuei. No marketplace we read lists it any more. MemoCat — Shared AI Memory is an MCP server published by MontyGovernance. Marketplaces we read that list it: 1 (Official MCP Registry). 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
MarketplaceamemMemoCat — Shared AI Memory
Community marketplace amanasmuei/amem Removed on 2026-10-17
Version: 0.15.0
Forks (GitHub): 1
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.4.3
Downloads/month (PyPI): 1 030
Downloads/week (PyPI): 54
Forks (GitHub): 4
Stars (GitHub): 28
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

amem vs MemoCat — Shared AI Memory
Factamemno longer listed · MemoCat — Shared AI Memory
Marketplaces that list it (differs)01
Stars (GitHub) (differs)228
Forks (GitHub) (differs)14
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@aman_asmuei/amem)On your machine (memocat-mcp)
Transport (differs)Not statedstdio
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)9Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/amanasmuei/amemgithub.com/montygovernance/memocat-mcp
Changes in the last 7 days (differs)20
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 amem

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

  • 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

  • Agentverse Memory

    Graph-native persistent memory for AI agents — 33 MCP tools, zero-LLM writes.

    by fetchai · MCP server

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

  • Mneme Memory

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

    by modusensus · MCP server

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

  • memory-mcp

    Persistent memory for Claude Code with hot cache instant recall and semantic search. Give your AI assistant a second brain.

    by Michael Denyer · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • total-recall io.github.Avi-Bendetsky/total-recall

    Persistent, verified, cross-session memory for AI agents. 26 tools. SQLite + sync.

    by Avi-Bendetsky · MCP server

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

  • Memento

    Persistent memory for AI tools. Local-first knowledge graph with hybrid search.

    by scrypster · MCP server

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

Its card, with similar plugins by marketplace

What each says it does

amem

In its own words, on Community GitHub marketplaces:

Persistent memory layer for AI — typed, scored, temporal, searchable. 28 tools, knowledge graph, privacy controls.

MemoCat — Shared AI Memory

In its own words, on Official MCP Registry:

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

How to run each

amem

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

MemoCat — Shared AI Memory As a local MCP server: PyPI package

Claude Code
claude mcp add --env "MONTYCAT_URI=<YOUR_MONTYCAT_URI>" --transport stdio memocat-mcp -- uvx memocat-mcp

Requires: MONTYCAT_URI (secret)

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

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

What it can do: amem · What it can do: MemoCat — Shared AI 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