Amneshia
Related Servers
Alternatives to Amneshia
- AlicenseAqualityBmaintenanceSelf-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.2488 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 gradedqualityDmaintenanceA 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.18MIT
- 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
- FlicenseNot gradedqualityAmaintenanceLocal 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.2-
- AlicenseNot gradedqualityBmaintenanceDynamic SQLite memory bank with semantic search, table management, and knowledge graphs for LLM agents.115 PyPI2MIT
- AlicenseNot gradedqualityBmaintenanceCross-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.700 PyPI2Apache 2.0
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: remember and remember_media handle writing, recall and context handle reading, and forget handles deletion. Descriptions explicitly cross-reference and differentiate use cases, making selection unambiguous.
Most names are lowercase action verbs (remember, recall, forget), but 'context' is a noun and 'remember_media' uses an underscore. These are minor deviations from an otherwise consistent and readable convention.
Five tools is well-scoped for a memory/knowledge graph server, covering the essential operations without redundancy. Each tool clearly earns its place.
The core lifecycle (create, read, delete) is covered, with update handled via remember as documented. Minor gaps like no explicit update tool or entity listing exist, but workarounds prevent dead ends.