A
licenseNot graded
qualityD
maintenanceAn MCP server that provides memory management tools for AI agents, enabling adding, searching, updating, and deleting memories via the Mem0 API.
22 npm
MIT
mem0-agent-memory
Related Servers
Alternatives to mem0-agent-memory
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server providing persistent memory for AI agents, enabling them to read, write, and query memories across sessions.94 npmMIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides AI agents with persistent memory capabilities through Mem0, allowing them to store, retrieve, and semantically search memories.684MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that provides AI agents with persistent memory, cross-agent sharing, and context management, enabling them to remember conversations, track complex tasks, and evolve skills across tools.2MIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server that extends AI agents' context window by providing tools to store, retrieve, and search memories, allowing agents to maintain history and context across long interactions.MIT
- AlicenseAqualityCmaintenanceMCP server for long-term agent memory, providing persistent memory, searchable knowledge, and evolving identity for AI agents.53Apache 2.0
TDQS
A4.2/5.0
Scored across 18 tools
Disambiguation4/5
The tools are largely distinct, with clear separation between CRUD, semantic search, metadata search, bulk operations, and export/import. The main potential confusion is among the multiple deletion tools (delete_memory, delete_all_memories, bulk_delete_memories, reset_memory) and between list_memories and get_recent_memories, but the descriptions clarify scope well.
Naming Consistency5/5
Tool names consistently follow a verb_noun snake_case pattern, with plural nouns for collection operations and singular nouns for single-item operations. Minor outliers like health_check and setup_steering are still readable and do not break the overall convention.
Tool Count4/5
Eighteen tools is slightly above the ideal range, but each tool occupies a reasonable niche in a comprehensive memory-management workflow. The count feels justified given coverage of CRUD, search, bulk deletion, import/export, stats, history, ingestion, and health checks.
Completeness5/5
The tool surface covers the full memory lifecycle: create, read, update, delete, search, bulk operations, backup/restore, analytics, and history. No critical dead ends are apparent for the stated purpose of agent/assistant memory management.
Maintenance
ActivityInactive
ResponsivenessNo issues