Lore
OfficialRelated Servers
Alternatives to Lore
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceCross-client AI memory hub for AI agents. Lets Claude Code, Cursor, Windsurf, and 20+ other clients share one physical SQLite memory database. Features bi-temporal time axes, source attribution, Q-Value usage-based ranking, and FTS5 full-text search with SQLite triggers.2,296 PyPI2Apache 2.0
- AlicenseNot gradedqualityDmaintenanceSelf-hosted, governed long-term memory and knowledge-graph server for AI agents with access control, hybrid retrieval, and typed graph linking.AGPL 3.0
- AlicenseNot gradedqualityAmaintenancePersistent shared memory for AI agents. Hybrid search (pgvector + tsvector), knowledge graph, cognitive scoring, and 16-language temporal extraction. 97.2% Recall@10 on LongMemEval with one PostgreSQL query. Works across Claude Code, Cursor, Codex, OpenClaw, and any MCP client.61 PyPI115MIT

Mnemo MCPofficial
AlicenseNot gradedqualityCmaintenancePersistent AI memory server with hybrid search and embedded sync. Enables AI agents to store, retrieve, and manage information across sessions with temporal knowledge graph support.MIT- AlicenseNot gradedqualityCmaintenanceSelf-hosted long-term memory for AI agents on your own Postgres. Facts are dated, versioned and superseded rather than silently overwritten, every recall ships with an inspectable trace, and agents can correct wrong memories from inside the conversation.2Apache 2.0
- AlicenseBqualityAmaintenanceLocal-first, auditable memory for Codex, Claude Code, and MCP clients. It stores scoped user/project memory in SQLite or Postgres, serves read-only recall and inspection tools by default, and supports opt-in governed writeback with review and forget controls.8635 npm18MIT
TDQS
Scored across 46 tools
While individual tools have detailed descriptions, the large number of memory-related tools (remember, remember_observation, add_conversation, ingest) and retrieval tools (recall, search, get_memories, related, graph_query) creates potential confusion for an agent. However, the descriptions attempt to differentiate use cases, and there are no truly overlapping tools.
Most tool names follow a verb_noun pattern using snake_case (e.g., list_memories, upvote_memory). However, there are exceptions like 'as_prompt' (starts with preposition), 'facts_at_time' (noun phrase), and 'on_this_day' (prepositional phrase). The overall pattern is fairly consistent but has several deviations.
With 46 tools, the server is quite large. While each tool serves a distinct purpose in the memory management lifecycle, the count exceeds what is typically manageable and may overwhelm agents. A more focused set could reduce cognitive load without losing functionality.
The tool surface covers the entire memory lifecycle: ingestion (multiple methods), retrieval (semantic, categorical, temporal, graph), maintenance (consolidation, supersession, forgetting, voting, sharing), auditing (provenance, history, conflicts), and export/import. It is exceptionally comprehensive for a knowledge management system.