Ext Ops Panel
Open dashboard
Comparison

hipocampus vs io.github.teflon07/memkeeper

hipocampus is a plugin bundle for AI coding tools published by kevin-hs-sohn. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.teflon07/memkeeper is an MCP server published by teflon07. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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
Marketplacehipocampusio.github.teflon07/memkeeper
Claude Code: claude-plugins-community Listed
Version: 0.2.1
Forks (GitHub): 12
Stars (GitHub): 211
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.5.3
Forks (GitHub): 0
Stars (GitHub): 4
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

hipocampus vs io.github.teflon07/memkeeper
Facthipocampusio.github.teflon07/memkeeper
Marketplaces that list it11
Stars (GitHub) (differs)211 (better)4 (worse)
Forks (GitHub) (differs)12 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (ghcr.io/teflon07/memkeeper:0.5.3)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)3Not published
Parts of the bundle (differs)8Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/kevin-hs-sohn/hipocampusgithub.com/teflon07/memkeeper
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

hipocampus

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

Persistent memory that survives across sessions. Hipocampus gives your agent a 3-tier memory system (hot/warm/cold) with a self-compressing 5-level compaction tree. Every session, the agent auto-loads a ~3K token topic index (ROOT.md) so it knows what it knows — then retrieves specific details on demand via tree traversal or hybrid search (BM25 + vector via qmd). All memory writes happen through subagents to keep your main session clean. Zero dependencies, zero infrastructure — just markdown files.

io.github.teflon07/memkeeper

In its own words, on Official MCP Registry:

Local-first memory for AI agents: on-device hybrid retrieval over a single SQLite file.

How to run each

hipocampus As a Claude Code plugin

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

io.github.teflon07/memkeeper As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio memkeeper -- docker run -i --rm ghcr.io/teflon07/memkeeper:0.5.3

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: hipocampus · What it can do: io.github.teflon07/memkeeper · 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