Skip to main content
Glama

Related Servers

Alternatives to Backstory

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Privacy-first personal knowledge database for your AI that ingests data exports (Google Takeout first) and exposes them via MCP tools like search and list items. Runs locally with no cloud or telemetry.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      A universal, local-first MCP hub that indexes personal files (documents, code, etc.) and provides private semantic search via hybrid dense+BM25 retrieval, enabling agents like Claude Desktop to query your data without sending it to the cloud.
      17
      6
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      A local MCP server that enables full-text and semantic search over your own Telegram chats using your personal MTProto login, with everything running locally.
      7
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Privacy-first local document search using semantic search. Runs entirely on your machine with no cloud services, supporting PDF, DOCX, TXT, and Markdown files.
      22
      9
      5,156 npm
      401
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables local browsing and searching of Skype export archives through MCP tools for messages, conversations, participants, and attachment extraction, with privacy-focused local processing.
      8 npm
      AGPL 3.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Offline AI-powered local file search MCP server for Windows. Searches inside document contents (Word, Excel, PDF, PowerPoint, HWP) using BM25 + dense vector hybrid search. 100% local, no cloud, no login, no telemetry.
      7
      Apache 2.0

    TDQS

    A3.6/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: event retrieval by ID, source listing, entity lookup, semantic timeline search, and time-range summarization. No overlap.

    Naming Consistency5/5

    All tools follow a consistent verb_noun snake_case pattern (e.g., get_events, list_sources), making naming predictable and clear.

    Tool Count5/5

    Five tools is appropriate for a focused query/summary server, covering core operations without being overwhelming or insufficient.

    Completeness4/5

    Covers key query scenarios (by ID, search, time range, source list) but lacks event mutations (create/update/delete), which fits the likely read-only domain. Minor gap: no direct way to get events by source.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues