Ext Ops Panel
Open dashboard
Comparison

amem vs io.github.tstockham96/engram

amem is a plugin bundle for AI coding tools published by Aman Asmuei. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.tstockham96/engram is an MCP server published by tstockham96. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-14. 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
Marketplaceamemio.github.tstockham96/engram
Community marketplace amanasmuei/amem Listed
Version: 0.15.0
Forks (GitHub): 1
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.5.1
Downloads/month (npm): 463
Downloads/week (npm): 109
Forks (GitHub): 6
Stars (GitHub): 47
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 1.0.0
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

amem vs io.github.tstockham96/engram
Factamemio.github.tstockham96/engram
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)2 (worse)47 (better)
Forks (GitHub) (differs)1 (worse)6 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@aman_asmuei/amem)On your machine (engram-sdk)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Hooks it runs (differs)3Not published
Parts of the bundle (differs)95
Licence (differs)MITProprietary
Repository (differs)github.com/amanasmuei/amemgithub.com/tstockham96/engram
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. 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

amem

In its own words, on Community GitHub marketplaces:

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

io.github.tstockham96/engram

In its own words, on Official MCP Registry:

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

How to run each

amem As a Claude Code plugin

Claude Code
/plugin marketplace add amanasmuei/amem
/plugin install amem@amem

io.github.tstockham96/engram As a local MCP server: npm package

Claude Code
claude mcp add --env "GEMINI_API_KEY=<YOUR_GEMINI_API_KEY>" --transport stdio engram -- npx -y engram-sdk

Requires: GEMINI_API_KEY (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: io.github.tstockham96/engram · 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. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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