OpenMemory MCP Server
Related Servers
Alternatives to OpenMemory MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceGives every Claude surface (claude.ai, Desktop, mobile, Office add-ins, Claude Code) read and write access to the memories, transcripts and notes produced by Claude Code instances on all of your machines, with hybrid keyword and semantic search. Runs as a self-hosted remote MCP server with GitHub allowlist authentication, secret redaction and audit logging.MIT
- FlicenseNot gradedqualityAmaintenanceEnables Claude Code to persistently add, search, update, and delete memories backed by self-hosted Qdrant vector storage, an optional Neo4j knowledge graph, and Ollama embeddings, using either Anthropic or a fully local LLM for fact extraction. It also exposes graph entity tools and session hooks so relevant context is automatically injected at startup and summaries saved on exit.-
- AlicenseAqualityAmaintenanceEnables personal AI memory management through MCP tools for adding, searching, exporting, and deleting memories, with knowledge-graph retrieval and multi-hop association for clients like Claude Desktop and Cursor.61Apache 2.0
- AlicenseNot gradedqualityBmaintenanceProvides Claude Desktop with persistent, structured memory and semantic search via a local SQLite knowledge graph, plus a web UI for visualization and management.MIT
- AlicenseAqualityBmaintenanceEnables Claude Desktop and compatible agents to search, read, add, update, and delete a locally stored, user-curated memory using hybrid retrieval with reranking and Qdrant. All processing runs locally without cloud services or API keys.921 PyPIApache 2.0
- FlicenseNot gradedqualityAmaintenanceEnables Claude Code to add, search, update, delete, and organize persistent memories across sessions using self-hosted Qdrant, Neo4j, and Ollama, with optional Anthropic or local LLM support. It also exposes tools for knowledge-graph entity relationship search and retrieval.-
TDQS
Scored across 8 tools
search_memories and semantic_search are clearly differentiated by keyword vs. meaning-based, though reinforce_memory overlaps with semantic_search's side effect of marking memories as seen and raising salience. The other tools (add, list, get, delete, health_check) are distinct.
All tools follow a consistent snake_case verb_noun pattern (search_memories, add_memory, list_memories, get_memory, delete_memory, reinforce_memory, health_check). health_check is a minor deviation but still clearly named.
Eight tools form a well-scoped set for a memory management server, covering search, CRUD, and health checks without bloat.
Core lifecycle (create, read, list, delete, search) and utility (health_check, reinforce) are covered. Missing an explicit update_memory tool, though the description suggests adding a corrected memory as a workaround.