mcp-memory-bank

   # MCP Memory Bank A personal long-term memory server for AI assistants, implemented as an MCP server (Model Context Protocol). Designed for individual use, not for teams. Allows you to save and restore context between sessions. Requires Python 3.10+. ## Version 1.1.3 ### What's new - Added validation that requires an absolute `project_id` in all storage modes. ## Version 1.1.2 - Fixed UTF-8 encoding when reading documents on Windows. ## Version 1.1.1 - Atomic file writes: Markdown documents are now written via temp file + `fsync` + `os.replace`, which prevents file corruption on crashes. - Resilient document parsing: invalid YAML frontmatter and malformed `tags` no longer break index synchronization. ## Why do you need this? ### 💰 Token savings The main cost when working with AI assistants (especially in development) comes from reading context. Every extra file read by the agent ends up in the context and is paid for on every request. Memory Bank solves this problem by: - At session start, the assistant only receives what matters most — documents with the `core` flag. - Other knowledge is loaded on demand, only when actually needed. - The agent stops aimlessly reading project files and immediately knows the architecture, current task, constraints, and status. ### 🧠 Long-term memory A regular assistant forgets everything after the chat is closed. Memory Bank preserves decisions made, architectural details, agreements, and any other important context between sessions. - No repeated explanations — the agent remembers why this particular database was chosen, what constraints were imposed, what architectural trade-offs were made. - When resuming work (even after a week or a month), the assistant is immediately up to date with the…