Memoria
Related Servers
Alternatives to Memoria
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceLocal-first memory for AI coding agents. Indexes your Claude Code, Codex, Cursor, Cline and Gemini CLI history by repo/branch/worktree and hands a context capsule (decisions, touched files, next steps) to the next agent over MCP.-
- AlicenseBqualityBmaintenanceGives AI coding agents a private local SQLite memory over MCP so Claude Code, Cursor, and Codex can share approved project lessons, conventions, decisions, and session history without cloud services or telemetry.28MIT
- AlicenseAqualityBmaintenancePersistent memory for AI coding agents, storing decisions, bug fixes, conventions, and discoveries in a local SQLite database and automatically recalling them when relevant. Works with Claude Code, Codex, Cursor, Gemini CLI, and other MCP-compatible agents.224MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude Code, Codex and other MCP agents to share one bounded, persistent memory across sessions, so a session starts from what earlier sessions learned instead of re-reading the repository. Storage and retrieval run locally on SQLite full-text search with per-client tokens and scopes, and optional local model enrichment, without any paid model in the path.1MIT
- AlicenseNot gradedqualityBmaintenanceExposes a unified local memory of conversations collected from Claude Code, Codex, Cursor, Gemini CLI, ChatGPT, claude.ai and Gemini over MCP, so any connected agent can search past work, browse and read conversations, and save notes that all tools can see. Optionally runs as a self-hosted node for web and mobile apps.1MIT
- AlicenseBqualityBmaintenancePersistent, local memory for AI coding agents that learns how you work, not just what you said. Supports Claude Code, Codex CLI, Cursor, and any MCP client.7998 PyPI77MIT
TDQS
Scored across 9 tools
The core CRUD operations (get_memory, remember, update_memory, forget) are cleanly distinct, and recall vs related vs file_context are differentiated by input type and intent. The main soft spot is the read-side overlap: project_context in 'full' mode and build_context both return a ready-made context block, and recall with a query partly duplicates build_context's optional query matches, though the descriptions do enough to steer selection.
There is no single convention: snake_case verb_noun (get_memory, update_memory, build_context), bare verbs (recall, remember, forget), and noun-only names (project_context, file_context, related) coexist. Each name is individually readable and snake_case formatting is uniform, but the verb-vs-noun alternation breaks predictability.
Nine tools is well within the sweet spot for a memory/knowledge server, and each one corresponds to a distinct step in the memory lifecycle (store, search, retrieve, relate, update, delete, assemble context). No tool appears redundant padding.
Full lifecycle is covered: create (remember), read (get_memory, recall, project_context, file_context, build_context), update (update_memory), delete (forget), and graph traversal (related). Minor gaps remain — no way to enumerate or browse all stored memories, filter by kind/project, or bulk-delete/prune stale entries.