Ext Ops Panel
Open dashboard
Comparison

memory-compactor vs io.github.tstockham96/engram

memory-compactor is a plugin bundle for AI coding tools published by sharooncs. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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-17. 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
Marketplacememory-compactorio.github.tstockham96/engram
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
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

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

memory-compactor vs io.github.tstockham96/engram
Factmemory-compactorio.github.tstockham96/engram
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)47 (better)
Forks (GitHub) (differs)0 (worse)6 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn 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
Parts of the bundle (differs)15
Licence (differs)MITProprietary
Repository (differs)github.com/sharooncs/claude-memory-compactorgithub.com/tstockham96/engram
Changes in the last 7 days00
First seen2026-10-112026-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

memory-compactor

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

Automatically monitors MEMORY.md size and warns Claude to compact it when it exceeds a configurable line threshold. Installs a PostToolUse hook on Write/Edit to memory directories, preventing auto-memory index overflow (only first 200 lines are loaded).

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

memory-compactor As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install memory-compactor@claude-community

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 memory-compactor publish no settings it asks for, so we do not compare settings.

What it can do: memory-compactor · What it can do: io.github.tstockham96/engram · 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