Skip to main content
Glama

Related Servers

Alternatives to Longhand

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      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
      33 npm
      7
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Persistent memory + FTS5 full-text search for Claude Code conversation history. Indexes ~/.claude/projects/ JSONL into SQLite, exposes 10 MCP tools (store/recall/search memories, browse sessions, get summaries) plus prompts. Includes a web UI for visual exploration
      10
      42 npm
      93
      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
      Provides persistent, searchable memory for Claude Code using local SQLite, semantic embeddings, and full-text search, enabling Claude to recall and retrieve context across sessions and projects without external services.
      6 npm
      4
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides local-first, cross-session memory for Claude Code, enabling semantic search across past sessions to retrieve procedures, decisions, or answers without exposing secrets.
      Apache 2.0
    • F
      license
      Not graded
      quality
      B
      maintenance
      Local semantic search over Claude Code sessions and shell command history, exposed to Claude Code as an MCP tool. Everything is indexed into one vector space and runs entirely on your machine.
      2
      -

    TDQS

    A3.7/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools have distinct purposes: 'recall' is the primary proactive memory, 'find_episodes' returns raw data, and 'search' is for semantic queries. However, 'search' and 'search_in_context' could be confused if descriptions are skimmed, and 'find_episodes' vs 'get_episode' might overlap for some users.

    Naming Consistency3/5

    Tools use a mix of verbs: 'find_', 'get_', 'list_', 'search', 'match_project', 'replay_file'. While all are lowercase with underscores, the verb choice is inconsistent. For example, 'find_commits' and 'get_session_commits' both retrieve commits but use different prefixes.

    Tool Count4/5

    17 tools is on the higher side but reasonable for a comprehensive memory server covering episodes, sessions, commits, and project status. Each tool has a specific retrieval niche, though some consolidation could reduce count slightly.

    Completeness4/5

    The tool set covers core retrieval needs: searching, getting details, timelines, and project status. It includes proactive recall and context-aware search. Minor gaps like a tool for counting or aggregating data, but overall it's well-rounded for read-only memory access.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive