Skip to main content
Glama
teflon07
by teflon07

Related Servers

Alternatives to memkeeper

  • 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
  • A
    license
    Not graded
    quality
    B
    maintenance
    A Model Context Protocol server that provides Claude CLI with a Graphiti knowledge-graph memory backed by Neo4j, featuring synchronous writes and no silent ingestion failures.
    Apache 2.0

Related Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    Lightweight persistent memory for AI agents using a single SQLite file with hybrid search (keywords + semantics). Zero to 12MB install, no cloud or server required.
    5
    MIT
  • A
    license
    A
    quality
    A
    maintenance
    Gives AI agents persistent, local-first memory using SQLite and on-device embeddings, enabling semantic search and recall across sessions with no cloud calls.
    8
    7
    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
    C
    maintenance
    A local-first memory engine for AI agents that stores embeddings in polar-quantized form in a single SQLite file, enabling private, compact, and human-like recall.
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Local-first, multi-user shared memory for AI agents with semantic search, offline support, and team synchronization.
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Local-first memory layer for AI agents. Compresses context with a local LLM and serves hybrid search over MCP.
    598 npm
    MIT

TDQS

A4.1/5.0

Scored across 16 tools

Disambiguation5/5

Every tool has a distinct role: memory retrieval, memory writes, graph traversal/curation, candidate review, and stats are clearly separated. Where overlap could occur (get vs search, pack vs graph_context, remember vs candidate_submit), the descriptions explicitly call out when to use which.

Naming Consistency3/5

Names are readable and consistently snake_case, but they mix single-word verbs (get, remember, forget, verify, pack), object_verb forms (memory_list, entity_search, candidate_submit), and noun phrases (graph_context, dream_graph, graph_neighbors). This makes the naming functional but not predictably patterned.

Tool Count4/5

At 16 tools, the set is slightly above the ideal 3–15 range, but the count is justified by the server's multiple subdomains: memory recall, memory mutation, graph projection, candidate review, and stats. Each tool earns its place without feeling redundant.

Completeness4/5

The server covers the full memory lifecycle for its design: write, retrieve, list, soft-delete, verify, and candidate-driven human review, plus graph curation and maintenance preview. Content updates are intentionally handled via writing a new memory and forgetting the old one; candidate approval/hard deletion are left to human/external channels, which is a reasonable boundary.

Maintenance

ActivitySlowing
ResponsivenessUnresponsive