kiro-recall
Related Servers
Alternatives to kiro-recall
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceA local, fully-offline MCP memory server that enables persistent storage and retrieval of information using SQLite with both keyword and semantic vector search capabilities.1022 npm13MIT
- AlicenseNot gradedqualityAmaintenanceA local-first MCP memory server that stores facts in SQLite with FTS5 full-text search, supports projects and pinned records, and optionally syncs to Obsidian, all without external API calls.3MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that provides semantic memory with search, related-content traversal, and write-back capabilities, all powered by local embeddings of your notes, documents, and chat histories.3MIT
- AlicenseNot gradedqualityDmaintenanceA fully local, self-hosted memory server for MCP clients (Claude Code, Cursor, etc.) that provides persistent memory storage with semantic search, using local embeddings and a local Qdrant vector store.MIT
- AlicenseAqualityBmaintenanceMCP server for persistent, cross-session, local-first memory for AI agents, storing memories as Markdown files with SQLite indexing for hybrid search.24Apache 2.0
- AlicenseNot gradedqualityBmaintenanceA local-first MCP memory server providing persistent, searchable memory for AI agents, powered by SQLite.1 npm1Apache 2.0
TDQS
Scored across 6 tools
Remember and Learn overlap because Remember accepts memory_type='lesson', which is essentially Learn's entire purpose. The other tools are clearly distinct, and the detailed descriptions help clarify priority and scope, but the lesson overlap creates real ambiguity.
Most tools use simple single-word verbs like Remember, Recall, Learn, and Forget, which is internally consistent. MemoryStats and PruneMemory break the pattern by using compound names, but the overall naming is still predictable and readable.
Six tools is well-scoped for a memory system. Each tool handles a distinct part of the lifecycle: storing, learning, recalling, forgetting, pruning, and inspecting statistics, with no unnecessary redundancy.
The core memory lifecycle is well covered: create, recall, delete, prune, and stats. The main gap is the lack of an update/edit operation for existing memories and no exact-key lookup, though agents can work around it by forgetting and re-remembering.