Thoth-Mem
Related Servers
Alternatives to Thoth-Mem
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceLocal-first memory for AI coding agents using SQLite, enabling persistent recall of decisions, lessons, and project context without cloud or API keys.10107 PyPI281Apache 2.0
- AlicenseNot gradedqualityNot gradedmaintenanceProvides AI coding agents with persistent, long-term memory through local semantic search and SQLite storage. It enables agents to save and retrieve architectural decisions or project context across different conversation sessions without requiring cloud services.MIT
- AlicenseNot gradedqualityDmaintenanceProvides AI coding assistants with persistent project memory to retain architectural decisions, code patterns, and domain knowledge across sessions. It stores data locally in a SQLite database, allowing agents to remember, recall, and manage project-specific context using full-text search.8 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceGives AI coding agents persistent memory by storing observations, decisions, and learnings in a local SQLite database with vector search, full-text search, and a rules engine.4MIT
- AlicenseNot gradedqualityDmaintenancePersistent memory for AI coding agents with local-first, zero-cost, privacy-first SQLite/FTS5 storage and biological-inspired decay.11 npm3MIT
- AlicenseAqualityBmaintenanceProvides persistent cross-session memory and full-text search for AI coding assistants, storing project context, decisions, and preferences while enabling searchable access to conversation history via local SQLite.81MIT
TDQS
Scored across 6 tools
Each tool has a distinct role: mem_save writes, mem_get expands a specific id, mem_recall searches, mem_context builds continuity, mem_project inspects views, and mem_session records lifecycle events. However, the retrieval-oriented tools (mem_recall, mem_context, mem_project) overlap conceptually, and mem_save vs mem_session require explicit guidance ('never use it as an ordinary save'), signaling residual ambiguity.
All six tools use a consistent mem_ prefix followed by a concise snake_case noun/verb (mem_get, mem_save, mem_recall, mem_context, mem_project, mem_session). The pattern is predictable and uniform throughout.
Six tools is well-scoped for a memory server, covering write, expand, search, context, project inspection, and lifecycle in a compact surface. Each tool clearly earns its place with no redundancy or padding.
The surface covers the full memory lifecycle: saving, searching, expanding, context building, project inspection, and session lifecycle recording. A delete/forget or update operation appears absent, a minor gap agents could work around in an append-oriented memory model.