mcp-automem
Related Servers
Alternatives to mcp-automem
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables 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 gradedqualityAmaintenanceProvides 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 clearly distinct operation: store, recall, associate, update, delete, and health-check. Even though recall_memory has multiple modes, the mode selection is explicit and non-overlapping with other tools.
The core tools follow a consistent verb_noun pattern: store_memory, recall_memory, update_memory, delete_memory. Minor deviations are associate_memories (plural) and check_database_health (different object noun), but the convention remains predictable and readable.
Six tools is well-scoped for a memory server: basic CRUD, relationship management, and health checking. Each tool serves a distinct purpose and none feel redundant or excessive.
The tool surface covers the full memory lifecycle: store, recall, update, delete, and graph association. Recalled enumeration and bulk delete modes also cover maintenance/audit workflows, leaving no obvious dead ends.