Skip to main content
Glama

Related Servers

Alternatives to kb-memory

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Durable hybrid memory for AI agents. Combines vector search, BM25, temporal retrieval, and optional Memgraph knowledge graph via reciprocal rank fusion. 6 MCP tools: health, search, answer, feedback, graph_query, graph_add_triple. Self-hosted with Qdrant backend.
      7
      278 PyPI
      9
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that enables persistent, hybrid, local memory for LLM agents, with vector + BM25 search, knowledge graph, and policy-driven retention, providing token-budgeted context injection for AI assistants.
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Local-first, cross-agent memory layer for Hermes, OpenClaw, and Claude Code (MCP) behind a single REST API. Hybrid BM25+pgvector+RRF retrieval with optional Qwen3 rerank, a three-stage "dream" consolidation cycle (Light → REM → Deep) that clusters and de-dupes daily memories into durable knowledge with a narrative journal written to Obsidian, and a persistent 6-dimension emotion state machine that
      8
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Local-first memory layer for AI agents. Compresses context with a local LLM and serves hybrid search over MCP.
      674 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Persistent memory MCP server for AI coding agents (Claude Code, Codex, Gemini CLI). Hybrid retrieval (vector + BM25), cross-encoder reranking, knowledge graph, session checkpoint/resume, and multi-scope isolation. Local-first with LanceDB.
      30
      50 npm
      15
      MIT

    TDQS

    A3.7/5.0

    Scored across 11 tools

    Disambiguation4/5

    The memory CRUD set (write/read/update/delete/search) is clearly differentiated, as are link/unlink/list_links and add_document/add_webpage. The only mild overlap is between ask_kb (RAG answer) and search_memory (raw retrieval), but their descriptions make the answer-vs-hits distinction clear.

    Naming Consistency4/5

    Names follow a consistent snake_case verb_noun pattern (write_memory, read_memory, link_memory, unlink_memory, add_document, ask_kb). Minor deviation: 'write_' and 'add_' both serve creation, and list_links/ask_kb omit the 'memory' noun, but conventions remain readable.

    Tool Count5/5

    11 tools is well within the ideal 3-15 range and each tool earns its place across distinct clusters (CRUD, linking, ingestion, retrieval/Q&A). No redundant or trivial tools.

    Completeness4/5

    Core lifecycle is covered: full memory CRUD plus search, complete link/unlink/list linking, document and webpage ingestion, and RAG Q&A. Minor gaps exist (e.g. no listing/browsing of all memories, no bulk or tag-based management, no document update/re-ingest), but agents can work around these via search.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues