Skip to main content
Glama

Related Servers

Alternatives to loreroom

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server and background daemon that captures Discord and Telegram conversations locally to provide persistent memory for Claude Code sessions. It enables hybrid search and automatic context injection of chat history to maintain continuity across development sessions.
      16 npm
      22
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Persistent memory for Claude Code. Automatically indexes every conversation and provides production-grade hybrid search (BM25 + vectors + reranker) via MCP tools. 100% local, zero config, zero API keys, zero invoice.
      16
      50 npm
      7
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Persistent local memory for Claude Code that indexes every session's JSONL file verbatim into SQLite + ChromaDB. Exposes 17 MCP tools for semantic recall, deterministic file replay, and fuzzy "do you remember when..." queries across your entire session history — no API calls, nothing leaves the machine.
      17
      367 PyPI
      14
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      Long-term memory MCP server for Claude Code with SQLite persistence, encryption, semantic search, and automatic memory linking.
      22 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides persistent semantic memory for Claude Code via local embeddings and six MCP tools, enabling context storage and retrieval across sessions without cloud dependencies.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A lightweight MCP server that gives Claude Code Channels on Telegram persistent memory by storing facts, conversation logs, and session summaries in Supabase.
      8 npm
      10
      MIT

    TDQS

    A4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one retrieves recent context by time, the other searches history by keywords. There is no overlap.

    Naming Consistency5/5

    Both tools use consistent snake_case naming with a verb_noun pattern (get_recent_context, search_tg_history), making them predictable.

    Tool Count3/5

    With only 2 tools, the server feels thin for its intended purpose of Telegram history retrieval, but it is borderline as it covers two essential retrieval methods.

    Completeness3/5

    The tool set covers time-based and keyword-based retrieval, but lacks other potentially useful operations like retrieving by user or date range, leaving notable gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues