memory_mcp
Related Servers
Alternatives to memory_mcp
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.1011 npm1MIT
- AlicenseNot gradedqualityCmaintenanceProvides 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.2 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.6 npm1MIT
- 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 4 tools
Each tool maps to a distinct operation (read a file, overwrite FACT.md, append to JOURNAL.jsonl, keyword-search JOURNAL), so an agent can select without confusion. The only mild proximity is read vs. search, but one is file-oriented and the other keyword-oriented in the journal, keeping them clearly separable.
All four tools follow the identical memory_<verb> snake_case pattern (read/update/append/search). No mixing of conventions or vague verbs.
Four tools is well within the appropriate range and each covers a distinct memory operation (retrieve, persist long-term, log event, query log). No redundant or filler tools.
The core memory lifecycle (read, overwrite FACT, append journal, search journal) is covered. Minor gaps remain: SOUL.md/USER.md are readable but not writable, and there is no delete or edit of individual journal entries, though agents can work around this via overwrite.