A
licenseNot graded
qualityD
maintenanceA local MCP server that gives AI coding agents persistent memory and context across sessions.
4 npm
MIT
LongtermMemory-MCP
Related Servers
Alternatives to LongtermMemory-MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI agents persistent, forgetting memory with layered decay, semantic search via token overlap, and zero external dependencies.MIT
- AlicenseNot gradedqualityDmaintenanceA self-hosted MCP server that gives AI agents persistent, searchable memory with importance scoring, knowledge graphs, and autonomous memory consolidation.1MIT
- AlicenseAqualityBmaintenanceA local MCP server that gives AI assistants persistent long-term memory using a biological neural architecture with cortex, synapses, and hippocampus.15311 npm8MIT
- FlicenseAqualityDmaintenanceA local-first MCP server providing persistent, project-scoped and global memory for AI agents using ChromaDB and Ollama embeddings, fully offline.7-
- FlicenseNot gradedqualityDmaintenanceA local MCP server that provides semantic memory storage and retrieval for coding and AI agents, enabling durable context across chat sessions.57 npm4-
TDQS
A3.9/5.0
Scored across 11 tools
Disambiguation4/5
The tools are mostly distinct: save/update/delete/backup/stats are clearly separate, and the search variants target semantic similarity, type, tags, and date range respectively. However, five retrieval-oriented tools (search_memory, get_all_memories, search_by_type, search_by_tags, search_by_date_range) create some choice ambiguity for an agent deciding how to fetch memories.
Naming Consistency4/5
Most names follow a predictable snake_case verb_noun pattern (search_memory, save_memory, update_memory, delete_memory, create_backup). Minor deviations include memory_stats, which is a noun phrase rather than an action, and the search_by_* family, but the overall convention is readable and consistent.
Tool Count5/5
With 11 tools, the set is well-scoped for a long-term memory server. Each tool covers a meaningful operation, and there is no excessive proliferation for the domain.
Completeness4/5
The surface covers core lifecycle operations: create, read/search, update, delete, bulk delete, stats, and backup/export. Minor gaps exist, such as no direct get-by-ID tool or restore/import operation, but agents can work around these using existing search and listing tools.
Maintenance
ActivityActive
ResponsivenessOutdated data