Ext Ops Panel
Open dashboard
Comparison

io.github.tstockham96/engram vs XMemo

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). XMemo is an MCP server published by yonro. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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
Marketplaceio.github.tstockham96/engramXMemo
Official MCP Registry Listed
Version: 0.5.1
Downloads/month (npm): 474
Downloads/week (npm): 109
Forks (GitHub): 6
Stars (GitHub): 47
Not marked · First seen
Listed
Version: 0.4.346
Downloads/month (npm): 1 599
Downloads/week (npm): 28
Forks (GitHub): 1
Stars (GitHub): 12
Not marked · First seen
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed

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

io.github.tstockham96/engram vs XMemo
Factio.github.tstockham96/engramXMemo
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)47 (better)12 (worse)
Forks (GitHub) (differs)6 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (engram-sdk)Remote server (xmemo.dev/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 12, secrets among them: 1
Parts of the bundle (differs)5Not a bundle
Licence (differs)ProprietaryNot stated
Repository (differs)github.com/tstockham96/engramgithub.com/yonro/memory-os-cli
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 days ago, requires a key

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

io.github.tstockham96/engram

In its own words, on Official MCP Registry:

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

XMemo

In its own words, on Official MCP Registry:

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

How to run each

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)

XMemo As a remote MCP server

Claude Code
claude mcp add --transport http xmemo https://xmemo.dev/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: XMEMO_KEY (secret), Authorization header

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only XMemo has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only io.github.tstockham96/engram asks for

  • GEMINI_API_KEY (secret)

Only XMemo asks for

  • XMEMO_KEY (secret)
  • XMEMO_URL

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: io.github.tstockham96/engram · What it can do: XMemo · Compare two other plugins

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