CarryMem
Related Servers
Alternatives to CarryMem
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceUniversal memory for AI agents and tools. Save, organize and search context anywhere.2-
- AlicenseNot gradedqualityDmaintenanceProvides a persistent, vendor-neutral memory layer that allows AI tools and agents to share context and knowledge across different platforms while maintaining local data ownership. It enables users to store, recall, and manage structured memories through hybrid semantic search and automated context assembly.14 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceA persistent memory layer for AI tools that decouples personal data from AI's unstable memory, enabling you to mention information once and have it remembered forever across all conversations.3MIT
- AlicenseNot gradedqualityCmaintenanceA vendor-neutral, user-sovereign memory layer for AI agents and tools, providing persistent, cross-tool memory that users fully own and control.17 npmApache 2.0

sovseal MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceProvides zero-knowledge, local-first persistent memory for AI assistants with on-device embeddings, cross-platform capture, and zero-RTT semantic recall.7Apache 2.0- AlicenseNot gradedqualityDmaintenanceProvides a shared, persistent memory layer for AI agents, enabling them to recall, memorize, and review user information across different applications.8MIT
TDQS
Scored across 31 tools
Several tools overlap in purpose: my_profile and get_memory_profile both surface summaries/statistics; list_rules and my_rules both list rules; match_rules and inject_rules both return applicable rules. That said, descriptions are detailed enough that an agent can usually pick the right one with careful reading.
All tool names use snake_case and mostly follow verb_noun (classify_message, recall_memories, delete_rule). A few outliers use possessive/noun phrases (my_profile, my_rules, shortest_path) or bare verbs (onboard), but the overall pattern is predictable.
31 tools is well past the 25-tool threshold and the surface is bloated: there are multiple overlapping recall and rules-listing tools that could be consolidated. The core memory domain is broad, but many tools feel like variants rather than distinct operations.
The memory lifecycle covers create, read, search, and delete, but update_memory is missing, forcing delete-and-recreate flows. Rules and knowledge base coverage are solid, and graph/consolidation features fill out the domain, so the gap is notable but not fatal.