openmemory-mcp
Related Servers
Alternatives to openmemory-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceSelf-hosted semantic memory for AI agents. Save worklogs, decisions, and notes via MCP, then recall them across sessions by meaning rather than keyword. Backed by Postgres + pgvector with local embeddings (multilingual-e5-base).1MIT
- AlicenseNot gradedqualityBmaintenanceSelf-hosted MCP memory server with a web UI, enabling multiple AI agents to share and manage persistent memories over a single SQLite store via HTTP.9 npmMIT
- AlicenseNot gradedqualityCmaintenanceA self-hostable MCP server that provides permanent memory for AI agents using Postgres + pgvector for semantic search and Markdown file sync.0MIT
- FlicenseNot gradedqualityAmaintenanceA local-first MCP memory server that lets AI coding agents store, search, and recall project-specific and cross-project knowledge, so architecture decisions, preferences, error patterns, and coding guidelines persist across sessions. It also exposes optional task-queue tools for handing off autonomous work that draws on the same stored context.-
- FlicenseNot gradedqualityBmaintenanceA self-hosted AI memory service that shares durable project context between MCP-compatible clients such as Claude Code and Devin, via a REST API and a Streamable HTTP MCP server with tools to remember, recall, list, and forget memories.-
- FlicenseNot gradedqualityBmaintenanceSelf-hosted AI memory system for coding assistants, providing project-scoped memory storage and retrieval via MCP tools (add, search, list, delete) to recall prior learnings without re-running discovery.1-
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: save, search, chronological listing, project discovery, and deletion. The search_memory vs memory_timeline overlap is explicitly addressed in descriptions, guiding correct selection.
Four tools follow a consistent verb_noun pattern (save_memory, search_memory, list_projects, delete_memory), but memory_timeline breaks the convention with a noun-first name. This is a minor deviation that remains readable.
Five tools is well-scoped for a memory server, covering the core lifecycle without bloat. Each tool earns its place and there are no redundant operations.
The surface covers create, search, list, and delete, which handles most memory workflows. However, there is no update/edit operation and no direct get-by-id, so agents must work around via delete-and-recreate or search.