Amneshia
Related Servers
Alternatives to Amneshia
- AlicenseAqualityCmaintenanceSelf-hosted personal knowledge graph for Claude that persists across sessions, devices, and tools. Built on Neo4j with local semantic embeddings; OAuth 2.1 lets Claude Code, Claude Desktop, and claude.ai web all hit the same graph.2345 npm2MIT

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
Related Servers
- AlicenseNot gradedqualityAmaintenanceZero-GPU, local-first, CPU-native cognitive memory layer for autonomous AI agents with hybrid search (LanceDB + SQLite FTS5), WebUI inspector, and multi-agent shared workspaces.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceA local memory engine for AI agents. Stores conversation episodes, consolidates knowledge through a neuroscience-inspired lifecycle, and builds a personal knowledge graph — all in a local SQLite database.17MIT
- AlicenseAqualityBmaintenanceEnables AI agents to persist facts with tags, sources, and importance in a local SQLite database, retrieve them through hybrid BM25 plus embedding search weighted by retention decay, link or supersede related entries, and review everything in a read-only visual dashboard showing the memory graph and timeline.6MIT
- AlicenseNot gradedqualityBmaintenanceLocal memory for AI agents in one SQLite file on your own machine. Facts carry a validity window and a confidence score, so an outdated one is superseded and downweighted rather than deleted, and retrieval fuses BM25, vector similarity and a knowledge graph.2AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceDynamic SQLite memory bank with semantic search, table management, and knowledge graphs for LLM agents.2MIT
- AlicenseNot gradedqualityAmaintenanceProvides long-term memory for LLMs via local SQLite storage with hybrid search (BM25, vectors, recency decay), enabling AI coding agents to persist and recall memories across sessions without cloud or API keys.53MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose with explicit WHEN TO USE and DO NOT USE cross-references: remember stores, recall does keyword search, context traverses graph relationships, and forget invalidates/removes. An agent can easily tell them apart.
All names are single lowercase words with no mixing of underscores or camelCase, which is consistent. However, 'context' is a noun while the other three (remember, recall, forget) are action verbs, a minor deviation from the otherwise consistent action-oriented pattern.
The 4 tools are perfectly scoped for a knowledge graph memory server, covering the core operations of store, search, graph traversal, and invalidation without redundancy. Each tool earns its place.
The surface covers the full lifecycle: remember handles create and update (with contradiction detection and authority tiers), recall and context cover different read patterns, and forget handles soft or hard deletion with cascading invalidation. No obvious gaps for the stated memory domain.