slowave
OfficialRelated Servers
Alternatives to slowave
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.276 npmMIT
- FlicenseNot gradedqualityAmaintenanceProvides a local-first persistent memory layer that lets AI coding agents store, recall, and semantically search project-specific and cross-project knowledge across sessions, so context, decisions, and guidelines survive between conversations. Runs entirely on the user's machine with SQLite and no API keys, and optionally supports autonomous task-queue execution built on the same memory.-
- FlicenseNot gradedqualityAmaintenanceProvides AI coding agents with a local-first persistent memory layer they can read and write during sessions, storing decisions, preferences, error patterns, and research per project or globally. Enables semantic and keyword search, formatted context recall, and cross-project guideline surfacing without API keys or cloud storage.-
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to store decisions, preferences, and lessons in a local SQLite store, then recall the most relevant ones on demand. Runs fully local — no cloud, API keys, or per-query cost — and also exposes forget and consolidate operations.2Apache 2.0
- AlicenseAqualityBmaintenanceGives AI agents persistent, local-first memory using SQLite and on-device embeddings, enabling semantic search and recall across sessions with no cloud calls.823 PyPI9MIT
- 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.-
TDQS
Scored across 5 tools
Each tool maps to a distinct phase of a documented cognitive cycle (activate/recall/remember/feedback/commit), and the descriptions explicitly separate the two retrieval tools (activate at task start vs. recall for deliberate mid-task lookups). The overlap between activate and recall is real but well-signposted, so misselection risk is low rather than zero.
All five tools use the same `slowave_` prefix plus a single lowercase verb in snake_case (activate, recall, remember, feedback, commit). No mixed conventions, no camelCase, no inconsistent verb/noun styles.
Five tools is tightly scoped to a memory lifecycle: open, read, write, assess, close. No tool appears redundant with another, and nothing feels like padding.
The lifecycle is fully covered end-to-end, including correction of stale claims via feedback with replacement IDs. However, there is no explicit forget/delete tool and no way to inspect or list what exists in a scope outside of retrieval, which leaves minor gaps for memory hygiene.