localmem-mcp
Related Servers
Alternatives to localmem-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to maintain persistent, local memory with retrieval-augmented search, knowledge graphs, and context surfacing, without any cloud dependencies.1,027 npmMIT
- AlicenseAqualityCmaintenanceLocal-first memory for AI agents. On-device hybrid retrieval over a single SQLite file.163Apache 2.0
- AlicenseNot gradedqualityBmaintenanceGives AI agents a private, on-device persistent memory using semantic search over stored facts, preferences, and decisions. It enables agents to remember information, recall it by meaning even without keyword overlap, delete memories, and list them by tag.1 npm4MIT

memiofficial
AlicenseNot gradedqualityBmaintenanceGives AI agents a local-first, persistent memory backed by a single SQLite file, letting them save decisions, preferences, and facts, then recall them by meaning or keyword across sessions and projects. Exposes tools for loading pinned context, searching, adding, updating, listing, and deleting memories, so agents stop forgetting between sessions.01Apache 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 gradedqualityCmaintenanceA local-first memory engine for AI agents that stores embeddings in polar-quantized form in a single SQLite file, enabling private, compact, and human-like recall.MIT
TDQS
Scored across 8 tools
Each tool targets a distinct operation (store, search, recall by id, list, update, delete, bulk delete, stats), and descriptions clearly separate search from recall and list. The only mild overlap is recall_memory's 'most recent memories' versus list_memories in chronological order, but the descriptions give enough guidance to choose correctly.
Most tools follow a consistent verb_noun pattern (store_memory, search_memory, update_memory, forget_memory), and all names are lowercase snake_case. memory_stats breaks the pattern by using a noun_noun form rather than a verb like get_stats, and singular/plural alternates between memory and memories.
Eight tools is well-scoped for a memory store: create, read (three retrieval modes), update, delete (single and bulk), and stats. Each tool earns its place without redundancy or bloat.
The surface covers the full memory lifecycle: store, retrieve by meaning/id/browse, update, delete, bulk prune, and inspect storage. There are no obvious dead ends; even bulk deletion is safely gated by requiring a filter.