#1 AIUnknown
engram — alternative #1 to zipmem-mcp
📇 🏠 🍎 🪟 🐧 - Local-first persistent memory for AI agents. SQLite + local embeddings (all-MiniLM-L6-v2), hybrid semantic + FTS5 recall, secret...
GitHub source
Recorded alternatives
Alternatives to zipmem-mcp
Every candidate below sits in AI. What ends up on this page is decided entirely by a recorded score — not by bidding, not by editor taste. Review both records, check current vendor terms, then decide.
#2 AIUnknown
memkeeper — alternative #2 to zipmem-mcp
🦀 🏠 🍎 🐧 - Local-first memory for AI agents: a single self-contained Rust binary over one SQLite file. Hybrid BM25/FTS + on-device ONNX embed...
GitHub source
#3 AIUnknown
enquire-mcp — alternative #3 to zipmem-mcp
📇 🏠 🍎 🪟 🐧 - Long-term memory for AI agents (Claude Code/Desktop, Cursor, ChatGPT, Codex, OpenClaw) backed by a local Obsidian markdown vault...
GitHub source
#4 AIUnknown
macos-vision-mcp — alternative #4 to zipmem-mcp
📇 🏠 🍎 - Local OCR and image analysis via Apple Vision Framework. Wraps macOS's native Vision API to expose OCR for images and PDFs (with rea...
GitHub source
#5 AIUnknown
memory-arbiter-mcp — alternative #5 to zipmem-mcp
🐍 🏠 🍎 🪟 🐧 - AI enhancement middleware: precise retrieval replaces full-memory loading (~80%+ token cut), rule-based conflict arbitration wit...
GitHub source10Apache-2.0
#6 AIUnknown
recallnest — alternative #6 to zipmem-mcp
📇 🏠 🍎 🪟 🐧 - Persistent memory MCP server for AI coding agents (Claude Code, Codex, Gemini CLI). Hybrid retrieval (vector + BM25), cross-enco...
GitHub source15MIT
#7 AIUnknown
mnemos — alternative #7 to zipmem-mcp
🏎️ 🏠 🍎 🪟 🐧 - Persistent memory engine for AI coding agents. Stores architecture decisions, bug root causes, and project conventions across s...
GitHub source
#8 AIUnknown
Myco — alternative #8 to zipmem-mcp
🐍 🏠 🍎 🪟 🐧 - Agent-first cognitive substrate with 18 manifest-driven verbs (germinate / eat / assimilate / sporulate / traverse / immune / mo...
GitHub source65MIT
Questions about this page
How were these alternatives selected?
Each candidate is a live catalogue record in the same primary category, picked by a deterministic score that Oryxen records in its catalogue: how many meaningful words the two listings share, whether their pricing classes oppose (a paid product against a free one), whether both are open source, and whether either record is featured. The same catalogue state always produces the same list — no randomness, no manual ranking.
Are these alternatives ranked by payment?
No. Rows are ordered only by the recorded score, highest first, with alphabetical ties — payment never influences the order, nothing here is paid placement, and Oryxen charges no listing or placement fee.
Always verify current terms with zipmem-mcp directly — Oryxen records pricing classes, not live quotes.