dev.mnemodb/mnemodb vs io.github.xultrax-web/agent-memory-mcp
dev.mnemodb/mnemodb is an MCP server published by mnemodb.dev. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.xultrax-web/agent-memory-mcp is an MCP server published by xultrax-web. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-30. 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
| Marketplace | ||
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.22 Downloads/month (npm): 1 452 Downloads/week (npm): 0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.15.0 Downloads/month (npm): 354 Downloads/week (npm): 87 Forks (GitHub): 0 Stars (GitHub): 1 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
| Fact | dev.mnemodb/mnemodb | io.github.xultrax-web/agent-memory-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 1 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-10-19 | Not published |
| Where it runs (differs) | On your machine (@mnemodb/mcp) | On your machine (@xultrax-web/agent-memory-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | 3, secrets among them: 0 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/mnemodb/mnemodb | github.com/xultrax-web/agent-memory-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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.mnemodb/mnemodb
Persistent agent memory as plain Markdown in your repo - readable, diffable, with provenance.
io.github.xultrax-web/agent-memory-mcp
Markdown memory for AI agents. Files you can read, edit, grep, and commit. Not a database.
How to run each
dev.mnemodb/mnemodb As a local MCP server: npm package
claude mcp add --transport stdio mnemodb -- npx -y @mnemodb/mcp
io.github.xultrax-web/agent-memory-mcp As a local MCP server: npm package
claude mcp add --transport stdio agent-memory-mcp -- npx -y @xultrax-web/agent-memory-mcp
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.mnemodb/mnemodb asks for
MNEMO_STORE
Only io.github.xultrax-web/agent-memory-mcp asks for
AGENT_MEMORY_DIRAGENT_MEMORY_LOGAGENT_MEMORY_SCOPE
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: dev.mnemodb/mnemodb · What it can do: io.github.xultrax-web/agent-memory-mcp · Compare two other plugins
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.