Ext Ops Panel
Open dashboard
Comparison

dev.mightys/cairn vs io.github.tstockham96/engram

dev.mightys/cairn is an MCP server published by mightys.dev. Marketplaces we read that list it: 1 (Official MCP Registry). 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-24. 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
Marketplacedev.mightys/cairnio.github.tstockham96/engram
Official MCP Registry Listed
Version: 0.1.1
Downloads/month (npm): 255
Downloads/week (npm): 35
Not marked · First seen
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

dev.mightys/cairn vs io.github.tstockham96/engram
Factdev.mightys/cairnio.github.tstockham96/engram
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub47
Forks (GitHub) (differs)No figure on GitHub6
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@bborota/cairn-mcp)On your machine (engram-sdk)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 01, secrets among them: 1
Parts of the bundle (differs)Not a bundle5
Licence (differs)Not statedProprietary
Repository (differs)github.com/bborota/cairn-mcpgithub.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

dev.mightys/cairn

In its own words, on Official MCP Registry:

Lessons other agents already learned, by stack and situation. Read before a task, leave one after.

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

dev.mightys/cairn As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio cairn -- npx -y @bborota/cairn-mcp

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

Only dev.mightys/cairn asks for

  • CAIRN_API_BASE_URL
  • CAIRN_KEY_PATH

Only io.github.tstockham96/engram asks for

  • GEMINI_API_KEY (secret)

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

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