Skip to main content
Glama
Sign In
losslesscut-mcp

losslesscut-mcp

by bariswha
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to losslesscut-mcp

No user-submitted related servers found.

    Related Servers

    • opencut-mcp

      kenimo49
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that enables LLM agents to control the OpenCut classic video editor's timeline through a Playwright-controlled browser, allowing automated video editing tasks like adding media, inserting clips, splitting, trimming, and exporting.
      9
      MIT

    • capcut-mcp

      dlyrr
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that reads and builds CapCut projects locally, enabling natural language queries about project contents, missing media, and creation of new edits including beat-synced cuts.
      6
      MIT

    • ffmpeg-mcp

      yuan66-hub
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides 17 FFmpeg-based tools for video and audio processing, including conversion, compression, and editing. It enables AI assistants to perform complex media tasks like extracting audio, adding watermarks, and merging videos using natural language.
      16,348 npm
      2
      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

    A3.6/5.0

    Scored across 22 tools

    Disambiguation4/5

    Most tools target clearly distinct operations (analysis, navigation, editing, export, diagnostics). There is mild overlap among the segment tools (set_cut_points, add_segment, set_segments) and the two frame tools (view_frames, contact_sheet), but descriptions explicitly contrast them and explain when to prefer one over the other.

    Naming Consistency4/5

    The dominant pattern is verb_noun (open_files, add_segment, set_cut_points, export_file, run_action, view_frames, check_tools). A few tools are noun-only (audio_levels, media_info, contact_sheet, keyframes), which is a minor deviation but still readable and consistent with a stable snake_case convention.

    Tool Count4/5

    At 22 tools it sits on the higher end of the ideal range, but each tool maps to a concrete, non-redundant capability spanning analysis, navigation, segment editing, export, and diagnostics. Nothing appears padded or duplicative, so the count is justified for a full media-cutting workflow.

    Completeness4/5

    The surface covers the whole lossless-cutting lifecycle: open/close, analysis (silence, black, scenes, audio levels, keyframes, frames), segment creation and selection, export with waiting, and generic action/diagnostics escape hatches. Minor gaps remain, such as reading back the current segment list or a merge/concat operation, but core workflows have no dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources