mem-plain
Related Servers
Alternatives to mem-plain
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenancePersistent memory server for MCP clients that lets AI assistants remember facts about users across sessions via a single markdown file, with tools to read, save, search, update, delete, and organize memory.10MIT
- AlicenseBqualityDmaintenanceLocal-first memory server for AI coding agents that stores work sessions, tasks, and durable memories in Markdown files, exposed through MCP tools for session management and memory retrieval.104 npm1MIT
- AlicenseNot gradedqualityDmaintenanceProvides a file-first personal memory layer for AI agents, enabling them to store and retrieve memories as markdown files with an SQLite index. The MCP server offers read-only search by default, with optional write tools for manual memory addition and conflict resolution.1 npmMIT
- AlicenseNot gradedqualityAmaintenanceServes a unified local memory bank over a stdio MCP server, exposing five tools and one resource so any MCP-capable harness can list, search, and read memories imported from Claude Code, Codex, Cursor, Kimi Code, and ZCode. It gives agents a single read-only view of user preferences, feedback, project state, and reference material stored as plain Markdown files.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP-speaking agents to read and write a local, portable, JSONL-based long-term memory, so context and durable facts persist across sessions through search, context injection, and memory lifecycle tools.35 npm2MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to store, retrieve, and manage persistent memories locally via an MCP server with hybrid vector and keyword search, plus tools for memory CRUD, search, backup, and import.MIT
TDQS
Scored across 5 tools
The five tools mostly map to distinct operations: read a file, append a journal event, search across memory, inspect stats, and overwrite FACT.md. The only mild overlap is between memory_read (which can also read FACT.archive.md) and memory_search (which surfaces archived lines), but the descriptions make the distinction clear.
All tool names follow the exact same `memory_<verb>` snake_case pattern. The verbs (read, append, search, stats, update) are predictable and readable.
Five tools is well-scoped for a personal memory server: one per core operation with nothing redundant. Each tool earns its place.
Read, append, search, stats, and overwrite are covered, but there is no way to delete or prune JOURNAL entries and no exposed mechanism to archive FACT.md into FACT.archive.md despite the archive file being a first-class concept. Agents can work around deletions by editing files externally, but the lifecycle surface has notable gaps.