Skip to main content
Glama
Sign In
local-video-scenes-mcp

local-video-scenes-mcp

by FlorinCiocirlan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to local-video-scenes-mcp

No user-submitted related servers found.

    Related Servers

    • watch-mcp

      Takinggg
      A
      license
      A
      quality
      B
      maintenance
      Enables Claude Code, Codex, Claude Desktop and Cursor to see and hear MP4/MOV/MKV/WebM videos and screen recordings through timestamped keyframe storyboards, zoom and full-resolution frame drill-down, and a locally generated Whisper transcript. It also works with recording bundles that capture clicks and typed context, and runs entirely on the user's machine with no uploads or API keys.
      5
      MIT

    • video-brief-mcp

      Artem-Pavlenko
      A
      license
      A
      quality
      C
      maintenance
      Converts screen-recorded walkthrough videos into timestamped transcripts, extracted frames, scene-change anchors, and interleaved slices that pair each frame with the speech following it, so a coding assistant can read video feedback. All processing runs locally via ffmpeg and Whisper, with results cached to disk and exportable as transcript, frame images, and a README skeleton.
      7
      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.
      448 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/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: checking availability, installing, extracting scenes, and cleanup. No overlap in functionality.

    Naming Consistency5/5

    All tools use a consistent 'video.' prefix and snake_case. The pattern verb_object (e.g., check_ffmpeg, extract_scenes) is maintained throughout.

    Tool Count5/5

    Four tools adequately cover the essential workflow for a video scene extraction server: environment check, installation, extraction, and cleanup. The scope is well-balanced.

    Completeness4/5

    The tool surface covers the core operations (check, install, extract, cleanup). A minor gap is the lack of a read-only tool to list previously extracted scenes without re-running extraction, but overall it's sufficient.

    Resources