Ext Ops Panel
Open dashboard
Comparison

io.github.daedalus/mcp-external-memory vs io.github.donggyun112/keymem

io.github.daedalus/mcp-external-memory is an MCP server published by daedalus. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.donggyun112/keymem is an MCP server published by donggyun112. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). 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
Marketplaceio.github.daedalus/mcp-external-memoryio.github.donggyun112/keymem
Official MCP Registry Listed
Version: 0.1.2
Downloads/month (PyPI): 87
Downloads/week (PyPI): 33
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.17.0
Downloads/month (npm): 1 919
Downloads/week (npm): 481
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.33.2
Downloads/month (npm): 1 919
Downloads/week (npm): 481
Forks (GitHub): 0
Stars (GitHub): 3
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.daedalus/mcp-external-memory vs io.github.donggyun112/keymem
Factio.github.daedalus/mcp-external-memoryio.github.donggyun112/keymem
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)3 (better)
Forks (GitHub)00
Last release (differs)Not published2026-10-22
Where it runs (differs)On your machine (mcp-external-memory)On your machine (keymem)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)Not statedMIT
Repository (differs)github.com/daedalus/mcp-external-memorygithub.com/donggyun112/keymem
Changes in the last 7 days (differs)04
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.daedalus/mcp-external-memory

In its own words, on Official MCP Registry:

An MCP server that gives LLMs persistent, searchable semantic memory

io.github.donggyun112/keymem

In its own words, on Official MCP Registry:

Associative key-graph memory for LLM agents — recall by association, not vector similarity.

How to run each

io.github.daedalus/mcp-external-memory As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio mcp-external-memory -- uvx mcp-external-memory

io.github.donggyun112/keymem As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio keymem -- npx -y keymem

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.daedalus/mcp-external-memory · What it can do: io.github.donggyun112/keymem · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). 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