kaeru memory
Related Servers
Alternatives to kaeru memory
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceLong-term memory for AI agents: a local-first knowledge graph (entities, observations, relations) with hybrid semantic + full-text search, sessions, tasks/bugs with status, and a live dashboard with a physics-based memory map. Self-hosted, installs with one command, no Docker required. Works with Claude Code, Cursor, VS Code, and any MCP or REST client.3-
- AlicenseAqualityBmaintenanceLocal-first memory engine for AI-agent teams: private/team/project ACL, associative recall, and federated sync across nodes. One SQLite file, no LLM required.127Apache 2.0
- AlicenseNot gradedqualityAmaintenanceLocal memory for AI agents in one SQLite file on your own machine. Facts carry a validity window and a confidence score, so an outdated one is superseded and downweighted rather than deleted, and retrieval fuses BM25, vector similarity and a knowledge graph.2Business Source 1.1
- AlicenseNot gradedqualityDmaintenanceA local memory engine for AI agents. Stores conversation episodes, consolidates knowledge through a neuroscience-inspired lifecycle, and builds a personal knowledge graph — all in a local SQLite database.18MIT
- AlicenseNot gradedqualityCmaintenancePersistent memory for AI agents with Ebbinghaus forgetting curve, semantic graph retrieval, and engineering state tracking. Local-first, DuckDB, zero cloud dependency.46 PyPI1MIT
- AlicenseAqualityBmaintenanceHermetic memory for AI agents — one Rust binary, one SQLite file, zero network. Recall returns evidence with provenance or abstains: no code path for making things up.229AGPL 3.0
TDQS
Scored across 35 tools
Many tools target related memory operations, and several boundaries are fuzzy: claim vs verdict both can save verdict evidence, note/reference/synthesise all create records, and context/read/search overlap in retrieval. Detailed descriptions mitigate much of the confusion, but an agent still has to reason carefully to choose the right tool.
All names are snake_case, but conventions are mixed: some are single verbs or nouns (task, claim, note, read), some are verb_noun (task_update, link_cloud), and others are noun_verb or noun_noun (initiative_manage, cloud_recall, board_config). The set is readable but does not follow a predictable pattern.
With 35 tools, the surface is heavy for a memory/knowledge server and includes many niche maintenance, sharing, and cloud-sync operations. While the domain is broad, the count exceeds a well-scoped set and likely burdens tool selection.
The surface covers an extensive memory lifecycle: creation, revision, replacement, relations, review, trails, lifecycle tiers, retention, audit history, search/read/context, initiatives, export, and cloud sharing. Minor gaps remain, such as no import counterpart to export and no obvious initiative creation action beyond management.