slowave
OfficialRelated Servers
Alternatives to slowave
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to maintain persistent, local memory with retrieval-augmented search, knowledge graphs, and context surfacing, without any cloud dependencies.31 npmMIT
- AlicenseAqualityAmaintenanceGives AI agents persistent, local-first memory using SQLite and on-device embeddings, enabling semantic search and recall across sessions with no cloud calls.87MIT
- FlicenseNot gradedqualityDmaintenanceProvides persistent AI agent memory using a local vector database for long-term semantic storage and short-term session scratchpads. It enables low-latency memory operations including search, storage, and bulk management without external cloud dependencies.-
- AlicenseBqualityAmaintenanceEnables AI agents to maintain a local, event-sourced long-term memory with semantic retrieval, decision confidence checks, and proactive recalls, ensuring data never leaves the machine.233MIT
- FlicenseNot gradedqualityAmaintenanceProvides persistent, local-first memory with knowledge graph and hybrid search for AI coding agents, reducing token usage by storing decisions, patterns, and codebase context.8-
- AlicenseNot gradedqualityCmaintenanceProvides persistent, searchable memory for AI agents across sessions using a four-tier memory system, without sending data to external APIs.1MIT
TDQS
Scored across 5 tools
Each tool occupies a distinct phase in the memory lifecycle: activate primes and opens a session, remember encodes facts, recall retrieves, feedback assesses retrieved items, and commit closes the task. There is no meaningful overlap, and the descriptions reinforce clear boundaries between start, use, and completion.
All tools follow a consistent slowave_<verb> pattern: activate, remember, recall, feedback, commit. The naming is uniform and predictable, making the intended action of each tool immediately clear.
Five tools is well-scoped for the stated purpose of managing a cognitive/memory session lifecycle. Each tool earns its place and together they form a compact, coherent set without redundancy or bloat.
The tool surface covers the full intended cycle: priming/activation, durable storage, retrieval, feedback on retrieval quality, and task closure with consolidation. Gaps like explicit deletion are handled through stale feedback, so no critical operation appears to be missing for the declared domain.