Ext Ops Panel
Open dashboard
Comparison

io.github.memtomem/memtomem vs M3 Memory

io.github.memtomem/memtomem is an MCP server published by memtomem. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). M3 Memory is an MCP server published by skynetcmd. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-18. 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.memtomem/memtomemM3 Memory
Official MCP Registry Listed
Version: 0.6.8
Downloads/month (PyPI): 1 652
Downloads/week (PyPI): 278
Forks (GitHub): 32
Stars (GitHub): 18
Not marked · First seen
Listed
Version: 2026.10.17.2
Downloads/month (PyPI): 5 393
Downloads/week (PyPI): 982
Forks (GitHub): 4
Stars (GitHub): 29
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.memtomem/memtomem vs M3 Memory
Factio.github.memtomem/memtomemM3 Memory
Marketplaces that list it22
Stars (GitHub) (differs)18 (worse)29 (better)
Forks (GitHub) (differs)32 (better)4 (worse)
Last release (differs)Not published2026-10-17
Where it runs (differs)On your machine (memtomem)On your machine (m3-memory)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 06, secrets among them: 0
Hooks it runs (differs)Not published3
Parts of the bundle (differs)822
LicenceApache-2.0Apache-2.0
Repository (differs)github.com/memtomem/memtomemgithub.com/skynetcmd/m3-memory
Changes in the last 7 days (differs)28
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.memtomem/memtomem

In its own words, on Official MCP Registry:

Markdown-first long-term memory for AI agents. Hybrid BM25 + vector search, runs locally.

M3 Memory

In its own words, on Official MCP Registry:

Local-first, cloud-friendly memory — 100+ tools, 99.2% LongMemEval-S retrieval@8, hybrid search.

How to run each

io.github.memtomem/memtomem As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio memtomem -- uvx memtomem serve

M3 Memory As a local MCP server: PyPI package

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

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 io.github.memtomem/memtomem asks for

  • MEMTOMEM_TOOL_MODE
  • ORT_DISABLE_TELEMETRY

Only M3 Memory asks for

  • LLM_ENDPOINTS_CSV
  • M3_AUTO_INSTALL
  • M3_CONFIG_ROOT
  • M3_EMBED_FALLBACK_URL
  • M3_EMBED_GGUF
  • M3_ENGINE_ROOT

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

What it can do: io.github.memtomem/memtomem · What it can do: M3 Memory · Compare two other plugins

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