A
licenseA
qualityB
maintenanceMemory manager for AI apps and Agents using various graph and vector stores and allowing ingestion from 30+ data sources
6
32,783
Apache 2.0
openmem-mcp
by bcmyguest
Related Servers
Alternatives to openmem-mcp
mem0-mcpofficial
AlicenseAqualityCmaintenanceSelf-hosted Mem0 MCP server integrating Qdrant, Neo4j, and Ollama for semantic memory search, graph entity relationships, and memory management via OpenMemory API.64MIT- AlicenseNot gradedqualityCmaintenanceConsolidates git history, test results, and Copilot sessions into a searchable SQLite database for AI assistants to answer questions about development activity.5MIT
- 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 gradedqualityAmaintenanceProvides AI coding agents with a persistent memory layer to save, recall, update, and track memories across sessions and repositories using hybrid semantic search.6MIT
- AlicenseNot gradedqualityBmaintenanceProvides 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
- 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.1 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
- FlicenseNot gradedqualityAmaintenanceProvides a local-first persistent memory layer that lets AI coding agents store, recall, and semantically search project-specific and cross-project knowledge across sessions, so context, decisions, and guidelines survive between conversations. Runs entirely on the user's machine with SQLite and no API keys, and optionally supports autonomous task-queue execution built on the same memory.-
TDQS
B3.2/5.0
Scored across 10 tools
Disambiguation4/5
Most tools have distinct operations, but memory_recall, memory_search, and memory_reflect overlap in retrieval/synthesis semantics. The descriptions clarify provider-specific behavior, which mostly resolves the ambiguity.
Naming Consistency5/5
All tools use a consistent snake_case memory_* prefix and clear verb/noun patterns. The naming is predictable across the entire set.
Tool Count5/5
Ten tools is well-scoped for a memory-provider abstraction layer. Each tool covers a meaningful operation such as add, search, export, status, consolidation, or scoping.
Completeness4/5
The surface covers creation, retrieval, deletion, import/export, provider status, synthesis, consolidation, and project scoping. Minor gaps exist around direct update or get-by-id operations, but core workflows are covered.
Maintenance
ActivityMaintained
ResponsivenessNo issues