Skip to main content
Glama

Related Servers

Alternatives to Amneshia

  • A
    license
    A
    quality
    C
    maintenance
    Self-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.
    23
    45 npm
    2
    MIT
  • A
    license
    A
    quality
    C
    maintenance
    Self-hosted Mem0 MCP server integrating Qdrant, Neo4j, and Ollama for semantic memory search, graph entity relationships, and memory management via OpenMemory API.
    6
    4
    MIT

Related Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    A 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.
    17
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Enables 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.
    6
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Local 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
    AGPL 3.0
  • A
    license
    Not graded
    quality
    A
    maintenance
    Provides 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.
    53
    MIT

TDQS

A4.5/5.0

Scored across 4 tools

Disambiguation5/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness5/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo issues