memkeeper
Related Servers
Alternatives to memkeeper
AlicenseAqualityCmaintenanceSelf-hosted Mem0 MCP server integrating Qdrant, Neo4j, and Ollama for semantic memory search, graph entity relationships, and memory management via OpenMemory API.64MIT
Geniro Graphiti MCPofficial
AlicenseNot gradedqualityBmaintenanceA Model Context Protocol server that provides Claude CLI with a Graphiti knowledge-graph memory backed by Neo4j, featuring synchronous writes and no silent ingestion failures.Apache 2.0
Related Servers
- AlicenseNot gradedqualityCmaintenanceLightweight persistent memory for AI agents using a single SQLite file with hybrid search (keywords + semantics). Zero to 12MB install, no cloud or server required.5MIT
- 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
- AlicenseNot gradedqualityBmaintenanceLocal 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.2AGPL 3.0
- 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
- AlicenseNot gradedqualityBmaintenanceLocal-first, multi-user shared memory for AI agents with semantic search, offline support, and team synchronization.MIT
- AlicenseNot gradedqualityBmaintenanceLocal-first memory layer for AI agents. Compresses context with a local LLM and serves hybrid search over MCP.598 npmMIT
TDQS
Scored across 16 tools
Every tool has a distinct role: memory retrieval, memory writes, graph traversal/curation, candidate review, and stats are clearly separated. Where overlap could occur (get vs search, pack vs graph_context, remember vs candidate_submit), the descriptions explicitly call out when to use which.
Names are readable and consistently snake_case, but they mix single-word verbs (get, remember, forget, verify, pack), object_verb forms (memory_list, entity_search, candidate_submit), and noun phrases (graph_context, dream_graph, graph_neighbors). This makes the naming functional but not predictably patterned.
At 16 tools, the set is slightly above the ideal 3–15 range, but the count is justified by the server's multiple subdomains: memory recall, memory mutation, graph projection, candidate review, and stats. Each tool earns its place without feeling redundant.
The server covers the full memory lifecycle for its design: write, retrieve, list, soft-delete, verify, and candidate-driven human review, plus graph curation and maintenance preview. Content updates are intentionally handled via writing a new memory and forgetting the old one; candidate approval/hard deletion are left to human/external channels, which is a reasonable boundary.