Skip to main content
Glama

Related Servers

Alternatives to Vindex MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables an agent to process local video files and then read, search and inspect the results: timestamped transcripts, on-screen text and key frames as images. Everything runs locally, so an agent can answer questions like how to perform a task shown in a screencast or meeting recording.
      84 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to query local video timelines by extracting speech, frame captions, and on-screen text into a SQLite store, exposing search and retrieval tools via MCP.
      PolyForm Noncommercial 1.0.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to perform local semantic searches over a user's own images and videos using natural-language queries, with tools for incremental indexing, status checks, and scope management while keeping data and inference on the local machine.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Let AI agents watch videos: local transcripts, speaker labels, scenes, chapters and exact-moment search from any video URL or file. Fully local, no API keys.
      4
      3
      AGPL 3.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to search what was said in local video and audio files and indexed web videos, returning matching files, exact timestamps, passages, and links, with everything processed offline on the user's machine.
      4
      MIT

    TDQS

    B3.4/5.0

    Scored across 5 tools

    Disambiguation4/5

    The tools generally have distinct roles across ingest, status, search, shot inspection, and transcript retrieval. There is some overlap because search_corpus and get_shot_context both return transcript/filmstrip context, and get_transcript can be confused with transcript fields returned by other tools, but the descriptions make the intended boundaries reasonably clear.

    Naming Consistency5/5

    All tool names use consistent snake_case with a clear verb_noun or verb_noun_object pattern: ingest_video, get_ingest_status, search_corpus, get_shot_context, get_transcript. The naming is predictable and easy to infer.

    Tool Count5/5

    Five tools is well scoped for a video ingestion and retrieval server. Each tool covers a distinct stage of the workflow from ingestion through search and contextual inspection, with no obviously redundant tools.

    Completeness4/5

    The core lifecycle is covered: ingest, check status, search, inspect shot context, and retrieve transcripts. Minor gaps remain around corpus/video management, such as listing ingested videos or deleting/removing bundles, which agents may need for cleanup or discovery.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data