mcp-automem
Related Servers
Alternatives to mcp-automem
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to have a living memory with atomic knowledge storage, multi-factor recall, organic decay, automatic learning, and graph traversal via MCP.1MIT
- FlicenseNot gradedqualityDmaintenanceA MCP server that provides persistent memory for AI assistants, storing personal information, relationships, and observations to enable personalized and contextual conversations.4-
- AlicenseAqualityDmaintenanceA persistent, self-organizing memory MCP server for AI assistants, using semantic search, knowledge graphs, and reinforcement learning to automatically manage and retrieve memories.13MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that gives AI assistants persistent memory across conversations, storing and retrieving user preferences and behaviors using vector search.11 npmMIT

kairnofficial
AlicenseNot gradedqualityBmaintenanceProvides AI assistants with a persistent knowledge graph and experience memory, featuring context-aware routing, progressive disclosure, decay-based forgetting, and automatic promotion of important knowledge. It offers 22 MCP tools for storing, recalling, connecting, and querying knowledge, experiences, preferences, and ideas.13MIT- AlicenseNot gradedqualityBmaintenanceA personal AI memory hub that stores and retrieves personal data from any MCP-enabled AI assistant, enabling persistent memory across conversations.5MIT
TDQS
Scored across 6 tools
Each tool targets a distinct operation (store, recall, update, delete, associate, health), and the mode-based descriptions make the boundaries mostly clear. The only real overlap is between store_memory's supersede mode and update_memory — both mutate an existing memory — but the descriptions do enough to steer an agent toward the right one.
All six tools follow a strict verb_noun snake_case pattern: store_memory, recall_memory, update_memory, delete_memory, associate_memories, check_database_health. No deviations or mixed conventions.
Six tools is well-scoped for a memory service: four CRUD ops, one graph-linking op, and one health check. Nothing feels padded or missing at the count level.
Full memory lifecycle is covered (create, read via three recall modes, update, delete, associate, health), including bulk and supersede paths. The notable gap is that associations, once created, cannot be removed or modified — there is no delete/update_association — so erroneous graph edges are permanent.