Mem0 MCP Serverofficial
A
licenseA
qualityF
maintenanceAn MCP server that integrates with mem0.ai to help users store, retrieve, and search coding preferences for more consistent programming practices.
9
662
Apache 2.0
dakera-mcp
Officialby Dakera-AI
Related Servers
Alternatives to dakera-mcp
- FlicenseNot gradedqualityDmaintenanceEnables Claude to store, search, and retrieve persistent memories using Zep Cloud's thread-based memory system for maintaining context across conversations.-
- AlicenseNot gradedqualityAmaintenanceA graph-based MCP server that provides AI coding agents with persistent memory to store patterns, track complex relationships, and retrieve knowledge across sessions. It leverages graph structures to handle temporal queries and relational paths that traditional vector stores often miss.247MIT
Related Servers
Recallofficial
AlicenseNot gradedqualityCmaintenanceOpen-source MCP memory server for AI agents — persistent, searchable, tiered memory across sessions. Works over stdio (Cursor, Claude Desktop) or HTTP+SSE. MIT licensed.8MIT- AlicenseNot gradedqualityBmaintenanceA self-hostable MCP server that provides permanent memory for AI agents using Postgres + pgvector for semantic search and Markdown file sync.6 npmMIT
- AlicenseAqualityAmaintenanceLocal MCP server giving AI coding agents (Claude Code, Cursor, VS Code/JetBrains Copilot) a shared, persistent memory of your projects and every bug/issue faced during development. Stateless, plain-file storage (AGENTS.md + issues.jsonl) — no database.1677 npm1MIT
- AlicenseNot gradedqualityAmaintenanceSelf-hosted MCP server giving AI agents persistent memory — Markdown source of truth, hybrid BM25+embedding search, typed graph relations.2MIT
- AlicenseNot gradedqualityDmaintenanceA local-first long-term memory system for AI coding agents, exposed as an MCP server.40 npmMIT
- FlicenseNot gradedqualityDmaintenancePersistent semantic memory MCP server for AI agents with hybrid search, LLM scoring, and decay engine, fully local.2-
TDQS
A3.6/5.0
Scored across 14 tools
Disambiguation3/5
Multiple search tools (dakera_recall, dakera_batch_recall, dakera_search, dakera_fulltext_search, dakera_hybrid_search) overlap in purpose, and dakera_forget/dakera_batch_forget share tag-based deletion. Descriptions help differentiate them, but an agent may still hesitate when choosing between semantic, keyword, hybrid, and filter-only retrieval.
Naming Consistency4/5
All tools use snake_case with a consistent dakera_ prefix, and most follow a verb_noun pattern (store, extract, recall, forget, session_start). Minor deviations like dakera_knowledge_graph and dakera_fulltext_search are noun phrases, but the overall convention is predictable.
Tool Count4/5
With 14 tools, the server is well within a reasonable range for memory and knowledge management. It covers CRUD, search, sessions, graph exploration, and meta-tool discovery, though the several search variants and meta tools make it slightly heavy.
Completeness3/5
Core lifecycle operations exist (store, recall/search, forget), but there is no update/upsert tool for memories or get-by-ID retrieval. Descriptions reference absent tools such as dakera_memory_importance and dakera_recall_associated, indicating notable gaps for a memory server.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive