Ext Ops Panel
Open dashboard
Comparison

io.github.HBarefoot/engram vs io.github.keshrath/agent-knowledge

io.github.HBarefoot/engram is an MCP server published by HBarefoot. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.keshrath/agent-knowledge is an MCP server published by keshrath. Marketplaces we read that list it: 3 (Official MCP Registry, Claude Code: claude-plugins-community, Community GitHub marketplaces). 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
Marketplaceio.github.HBarefoot/engramio.github.keshrath/agent-knowledge
Official MCP Registry Listed
Version: 1.6.3
Downloads/month (npm): 256
Downloads/week (npm): 46
Forks (GitHub): 1
Stars (GitHub): 9
Not marked · First seen
Listed
Version: 1.9.8
Downloads/month (npm): 1 018
Downloads/week (npm): 201
Forks (GitHub): 2
Stars (GitHub): 18
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 1.9.3
Forks (GitHub): 2
Stars (GitHub): 18
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

io.github.HBarefoot/engram vs io.github.keshrath/agent-knowledge
Factio.github.HBarefoot/engramio.github.keshrath/agent-knowledge
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)9 (worse)18 (better)
Forks (GitHub) (differs)1 (worse)2 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@hbarefoot/engram)On your machine (agent-knowledge)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle2
Licence (differs)Not statedMIT
Repository (differs)github.com/hbarefoot/engramgithub.com/keshrath/agent-knowledge
Changes in the last 7 days (differs)02
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

io.github.HBarefoot/engram

In its own words, on Official MCP Registry:

Local-first persistent memory for AI agents — SQLite + local embeddings, MCP-native, no cloud.

io.github.keshrath/agent-knowledge

In its own words, on Official MCP Registry:

Cross-session memory for AI agents - knowledge graph, scoring, semantic search

How to run each

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

Claude Code
claude mcp add --transport stdio engram -- npx -y @hbarefoot/engram start

io.github.keshrath/agent-knowledge As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio agent-knowledge -- npx -y agent-knowledge

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

Neither one's marketplaces publish the settings it asks for.

What it can do: io.github.HBarefoot/engram · What it can do: io.github.keshrath/agent-knowledge · 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. Data comes from public marketplace files in GitHub repositories of their authors. 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