living-memory-engine
Related Servers
Alternatives to living-memory-engine
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceSelf-hosted MCP server giving AI agents persistent memory for personalization and context across conversations.103 PyPI283Apache 2.0
- AlicenseAqualityBmaintenanceA self-hosted MCP memory server that gives every MCP-compatible agent a shared, persistent memory layer, so preferences, project conventions, and past decisions carry across sessions and across different agents and vendors. It combines hybrid keyword-plus-vector retrieval with automatic context injection, zero-config sync, and selective injection of memories by agent and priority.212MIT
- AlicenseNot gradedqualityBmaintenanceA self-hostable remote MCP server that gives multiple AI agents shared, durable, user-owned memory with semantic search, versioned documents, reusable skills, and lessons. It keeps each account isolated while running on the user's own Cloudflare deployment.MIT
- AlicenseAqualityDmaintenanceMCP server providing persistent memory for AI agents, enabling them to read, write, and query memories across sessions.915 npmMIT

Structured-shofficial
AlicenseNot gradedqualityDmaintenanceMCP server providing managed persistent memory for AI agents. Read and write structured state across sessions, tools, and restarts at 1000+ requests per second, with no infrastructure to self-host or operate.2Apache 2.0- AlicenseNot gradedqualityDmaintenanceA shared memory MCP server for AI agents that provides persistent, semantic memory across sessions and tools, enabling long-term recall and context sharing.9 npm12MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: add, search, summarize, and delete. There is no meaningful overlap between retrieval (search) and store-state inspection (state), and forget is explicitly destructive and separate.
All tools share a consistent memory_ prefix and lowercase style. memory_state is a noun where the others use action verbs, which is a minor deviation but does not create confusion.
Four tools is a well-scoped, focused set for a memory engine. Each tool covers a core need without unnecessary surface area or duplication.
The toolset covers the essential lifecycle: store, retrieve, inspect state, and delete. A precise single-item delete or explicit memory update would round it out, but the destructive substring delete plus memory_add makes common workflows workable.