Skip to main content
Glama
huseyinstif

klaket-mcp

by huseyinstif
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to klaket-mcp

No user-submitted related servers found.

    Related Servers

    • 9xvision by ASGARD-STUDIOS

      9xvisionofficial

      ASGARD-STUDIOS
      A
      license
      Not graded
      quality
      B
      maintenance
      Gives AI agents video perception by turning screen recordings, films and URLs into timestamped structured evidence: ordered UI states and transitions, per-screen OCR, shots, camera motion, palettes, on-screen text and speech, all cached locally with no API keys. Includes drill-down tools to zoom into intervals, crop full-resolution frames, diff two moments, and search on-screen text and speech across everything watched.
      2
      MIT

    • yueying

      vsh5dvsch7-png
      A
      license
      A
      quality
      A
      maintenance
      Enables AI clients to watch local video files or YouTube/Bilibili and other supported URLs, receiving timestamped transcripts, subtitles, searchable text and keyframe contact sheets. Runs fully offline with local speech recognition and bundled ffmpeg, so no API key or cloud upload is needed.
      6
      110 PyPI
      11
      MIT

    • video-context

      LaloHao
      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.
      21 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct purpose: ingest starts processing, job_status checks progress, get_result retrieves markdown, and find_moment searches within processed video. There is no functional overlap.

    Naming Consistency4/5

    All tools use the 'klaket_' prefix and snake_case, with three following a verb_noun pattern (ingest, get_result, find_moment) and one being noun_noun (job_status). The pattern is mostly consistent but has a minor deviation.

    Tool Count5/5

    With 4 tools, the server is well-scoped for its purpose of video ingestion and querying. Each tool serves a necessary step in the workflow without unnecessary bloat.

    Completeness4/5

    The tool set covers the core lifecycle (ingest, status, retrieve, search) but lacks deletion or listing capabilities. This is acceptable for a focused server, though minor gaps exist.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources