Mem0 MCP Server
OfficialRelated Servers
Alternatives to Mem0 MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceAn MCP server that enables users to store and retrieve personalized coding patterns, serving as a persistent memory layer for LLM agents. It allows AI models to generate code and refactor projects according to a user's specific styles, technologies, and established development conventions.71-
- AlicenseNot gradedqualityBmaintenanceMCP server that gives AI coding agents persistent memory across sessions, storing architecture decisions, past bugs, and codebase conventions locally.3 npmMIT
- AlicenseNot gradedqualityDmaintenanceA local MCP server providing persistent memory for AI coding assistants by storing and searching architectural decisions, patterns, and solutions. It also includes tools for git automation and mapping codebase expertise based on project history.MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides memory management tools for AI agents, enabling adding, searching, updating, and deleting memories via the Mem0 API.22 npmMIT
- AlicenseNot gradedqualityDmaintenanceA self-hosted MCP server that provides AI assistants with a shared, persistent SQLite-backed memory for storing and retrieving project context, decisions, and discoveries. It enables cross-session continuity and team-wide knowledge sharing to keep AI coding tools aligned and informed.3MIT
- AlicenseCqualityCmaintenanceAn MCP server that gives AI coding assistants persistent memory across sessions with chain-based project tracking, tickets, and structured handoffs.42GPL 3.0
TDQS
Scored across 9 tools
Most tools have distinct purposes, but get_memories and search_memories could cause confusion as both involve retrieving memories with filters, though search_memories adds semantic search. The other tools (add, delete, update, list) are clearly differentiated by their actions on memories or entities.
All tools follow a consistent verb_noun pattern (e.g., add_memory, delete_memory, get_memories), with clear and predictable naming. There are no deviations in style or convention across the set.
With 9 tools, this server is well-scoped for memory management, covering core operations like CRUD for memories and entities, plus search and listing. Each tool serves a clear purpose without redundancy or bloat.
The toolset provides complete coverage for memory management: create (add_memory), read (get_memory, get_memories, search_memories), update (update_memory), delete (delete_memory, delete_all_memories, delete_entities), and list (list_entities). No obvious gaps exist for the domain.