Stop re-explaining your project to your AI every session. memtomem turns your notes, docs, and code into a searchable memory that any MCP-compatible agent can use — across sessions, across agents, all on your machine.
All context is lost when a session ends. Architecture decisions, coding patterns, and debugging history must be re-explained every time.
Knowledge from Claude Code can't be carried over to Cursor. Each agent is trapped in its own isolated memory silo.
Current memory systems only work when agents explicitly search, are locked to specific runtimes, and offer only a single LTM layer.
Index your notes, docs, and code with mm index, then find them with hybrid search — BM25 keyword and dense-vector semantic search fused via RRF, so exact identifiers and meaning-based queries both land. Markdown, code, and structured files are chunked by structure, and re-indexing only re-embeds the chunks that changed.
Memory doesn't vanish when a session ends. Namespaces split each agent's private space from a shared space, and the session workflow lets one agent pick up what another already worked out. Claude Code, Cursor, and Codex all share one memory store.
Sync skills, commands, and subagents from one canonical .memtomem/ source out to every AI runtime. Handle per-row Sync/Import in the mm web Simple view, move artifacts across projects and tiers with mm context copy/move, and bulk-sync many projects with mm context sync --all-projects.
Your agent doesn't have to ask. STM observes the MCP calls it proxies and surfaces relevant memories at the right moment. Each surfaced memory carries an id, so your agent can rate or invalidate individual items.
Every MCP tool response passes through STM before it reaches your agent. When a response exceeds the context budget, one of 8 strategies is auto-selected by content type to cut tokens. The active query shapes the budget — relevant sections get more room, so the information your agent needs is preserved.
SQLite + ONNX under the hood — no GPU, no external API, no cloud. SQLite files are kept at 0600, secret-looking responses are never cached, and secrets are never pushed out. The STM proxy is fully reversible with mms eject, so there's no lock-in.
From install to first memory in under 5 minutes. uv tool install → interactive mm init → ask your agent.
GuideHow BM25 + vector + RRF fusion search works and how to tune it.
LTM8 strategies, auto-selection logic, and query-aware budget allocation.
STM5-level gating, feedback loop, min_score auto-tuning deep dive.
STM5-step session workflow, namespace inheritance, cross-agent sharing.
LTMSync and Import from the Simple view, copy/move between projects, and bulk-sync many projects at once.
LTMNo GPU. No external services. One uv install is all you need.