Survey of Local-First Markdown Memory Servers for AI Agents: Mem0, Hindsight, Zep, and the Newcomer Engram
A Reddit user asked for a fully local agent memory system that stores memories as readable Markdown files — not a database or cloud service. After receiving ~20 suggestions and testing them all, here is the breakdown of what each tool actually offers and where the gaps remain.
Non-Memory Systems Flagged
Several suggested tools are not memory systems: ChromaDB is a vector database; qmd is a document search engine with no write pipeline; ContextKeep does context compression; LCM preserves session context only.
Established Options
- mem0 — market leader, graph-based memory, SDKs in multiple languages, production-scale. Downsides: defaults to OpenAI, leans hosted, stores in opaque database.
- Hindsight — knowledge graph, entity resolution, handles contradictory memories. Requires Postgres + vector DB, storage is SQL — can't read files directly.
- Zep — longest track record, multi-modal memory, structured extraction. Cloud-first, similar infra requirements to Hindsight.
- Honcho — continual learning, stateful architecture, more research-grade. AGPL license + cloud dependency.
OpenClaw-Specific Options
- memory-lancedb-pro — strongest memory plugin for OpenClaw, hybrid retrieval, decay model, actively maintained. Not a standalone server.
- GBrain — MCP-first, decent OpenClaw integration, not useful outside ecosystem.
Most Interesting Newcomer: mnem
mnem is a Rust single binary, no Python/Ollama/external dependencies. Described as "git for agent memories": branch, diff, merge, revert. Uses GraphRAG. Benchmarks well against mem0. Two weeks old — thin test coverage. Storage is content-addressed graph nodes, not readable files.
The Gap and What Fills It: Engram
None of the tested tools combined fully local + human-readable file storage + smart deduplication + importance decay + standalone server with no infrastructure requirements. Engram by Obsidian68 (github.com/Obsidian68/Engram) is brand new (almost no stars) but checks all four boxes:
- Memories stored as Markdown files in a folder — openable in VS Code, editable, deletable.
- Full REST API and MCP server.
- Smart dedup on writes, importance decay for older memories.
- Runs entirely on Ollama — no API keys, no external calls, fully local.
If privacy and readability matter for your agent's knowledge, Engram is currently the only complete solution.
📖 Read the full source: r/openclaw
👀 See Also

Aura Research: Local tool compiles documents into AI-navigable wiki with persistent memory
Aura Research is an open-source tool that processes raw documents (PDFs, papers, notes, code, 60+ formats) into a structured markdown wiki with backlinked articles, concept pages, and a master index. It compresses everything into a .aura archive optimized for RAG retrieval and runs 100% locally with no data leaving your machine.

Two MCP Tools for Claude Code: Idea Validation and Trading Agent Memory
A developer built two MCP tools for Claude Code: idea-reality-mcp checks GitHub and Hacker News before coding to avoid duplicates, while tradememory-protocol provides memory for AI trading agents to store trades with context and track strategy performance. Both are open source and available on PyPI.

Bio-Inspired Memory System for Local LLMs: LTP and Selective Oblivion Implementation
A developer built a local MCP server implementing bio-inspired memory mechanics including Long-Term Potentiation reinforcement, selective oblivion decay, and weekly consolidation cycles. The system uses hybrid search with sqlite-vec and text fallbacks, non-blocking architecture with asyncio executors, and maintains state via a persistent 'Soul' file.

Tripsy Launches MCP Server for Claude: Manage Trips via Structured API
Tripsy's official MCP server lets Claude directly read, create, and update trips, activities, stays, transportation, and expenses. Setup takes ~1 minute via Claude's custom connector.