Ext Ops Panel
Open dashboard
Comparison

cogmemai-memory vs io.github.tstockham96/engram

cogmemai-memory is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑22.

cogmemai-memory is a plugin bundle for AI coding tools published by hifriendbot. No marketplace we read lists it any more. 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-28. 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
Marketplacecogmemai-memoryio.github.tstockham96/engram
Community marketplace hifriendbot/cogmemai-mcp Removed on 2026-10-22
Version: not stated
Forks (GitHub): 3
Stars (GitHub): 7
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.5.1
Downloads/month (npm): 474
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

cogmemai-memory vs io.github.tstockham96/engram
Factcogmemai-memoryno longer listed · io.github.tstockham96/engram
Marketplaces that list it (differs)02
Stars (GitHub) (differs)747
Forks (GitHub) (differs)36
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)Not statedProprietary
Repository (differs)github.com/hifriendbot/cogmemai-mcpgithub.com/tstockham96/engram
Changes in the last 7 days (differs)20
First seen (differs)2026-10-132026-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 cogmemai-memory

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

  • MCP AutoMem

    Graph-vector memory for AI assistants using FalkorDB and Qdrant

    by verygoodplugins · MCP server

    Listed on: Official MCP Registry, Community GitHub marketplaces · Describes nearly the same job

  • engram

    Persistent memory with session tracking, compaction recovery, and Memory Protocol. Gives Claude a brain that survives across sessions.

    by Gentleman Programming · Plugin bundle

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

  • basic-memory

    The bridge between Claude's working memory and Basic Memory's durable knowledge graph — session briefings, pre-compaction checkpoints, and capture reflexes

    by Basic Machines · Plugin bundle

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

  • Memory

    Active memory writing during conversation, plus manual /memory:consolidate with theme clustering, ground-truth prune, adversarial pass, and machine validator — no…

    by Frad LEE · Plugin bundle

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

  • mcp-memory-service

    Semantic memory for Claude Code sessions

    by doobidoo · Plugin bundle

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

  • XMemo

    Shared, governed long-term memory for AI agents across tools and sessions via MCP and REST.

    by yonro · MCP server

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

Its card, with similar plugins by marketplace

What each says it does

cogmemai-memory

In its own words, on Community GitHub marketplaces:

Teaches Claude best practices for memory management — when to save, importance scoring, memory types, and session workflows.

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

cogmemai-memory

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

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

What it can do: cogmemai-memory · 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