openmem-mcp
Related Servers
Alternatives to openmem-mcp
- AlicenseAqualityBmaintenanceMemory manager for AI apps and Agents using various graph and vector stores and allowing ingestion from 30+ data sources633,348Apache 2.0

mem0-mcpofficial
AlicenseAqualityDmaintenanceSelf-hosted Mem0 MCP server integrating Qdrant, Neo4j, and Ollama for semantic memory search, graph entity relationships, and memory management via OpenMemory API.64MIT- AlicenseNot gradedqualityDmaintenanceConsolidates git history, test results, and Copilot sessions into a searchable SQLite database for AI assistants to answer questions about development activity.6MIT
- AlicenseNot gradedqualityCmaintenanceEnables Muse Code to store and retrieve long-term memories via Hindsight, providing recall, retain, reflect, and status operations shared across coding agents.MIT
Related Servers
- AlicenseNot gradedqualityBmaintenanceProvides AI coding agents with a persistent memory layer to save, recall, update, and track memories across sessions and repositories using hybrid semantic search.5MIT
- AlicenseNot gradedqualityDmaintenanceProvides persistent, local-first memory for coding agents with Markdown as the source of truth, exposed via CLI, loopback API, MCP, and Codex hooks for context retrieval and durable writes.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to store, search, and recall project-scoped episodic memories across IDEs and sessions, with SQLite FTS5/BM25 ranking, telemetry, and import/export tools.MIT
- AlicenseAqualityBmaintenanceProvides persistent, searchable memory across AI coding agent and chat history (Claude Code, Codex, Gemini CLI, ChatGPT, and more) via retrieval-augmented generation, enabling semantic and hybrid search to retain context across sessions.5MIT
- AlicenseNot gradedqualityDmaintenanceShareable memory for AI coding agents. Enables agents to remember and recall durable memories across sessions and share them as importable packs.4 npmMIT
- AlicenseNot gradedqualityBmaintenanceProvides persistent memory for AI coding agents, enabling them to save, search (hybrid vector/BM25/concept graph), list sessions, and forget memories via MCP tools.11 npmApache 2.0
TDQS
Scored across 15 tools
The three retrieval tools (search/recall/reflect) overlap conceptually, but each description explicitly says when to use which (raw hits vs. context vs. synthesized answer), which resolves most of the confusion. memory_status vs. memory_provider_status are also close (ingest drain vs. provider id/URL) but are distinguishable by their stated outputs; memory_add vs. memory_import is clear from the PMM payload requirement.
Every name uses the memory_ prefix in snake_case, giving a strong shared convention. The only deviation is word order: memory_pages_list/search/read put the verb last while memory_add, memory_search and memory_forget put it directly after the prefix, so the pattern is predictable but not perfectly uniform.
15 tools sits at the top of the sensible band and is justified by the breadth of the surface: three provider backends, ingest lifecycle, pages and export/import. Nothing looks like filler, though the provider-specific optionality (Hindsight-only, mem0-only, Cognee-only tools) means several tools are dead for any given user.
Storage, retrieval, sync, backup and page reading are covered, but there are clear gaps: no memory_update/overwrite tool, and knowledge pages can be listed, searched and read but not edited or deleted except by dropping a whole bank via memory_forget. Page creation exists only through memory_capture_initiative for feature plans, so an agent cannot add or revise a convention page directly.