Skip to main content
Glama
Sign In
Reelwright

Reelwright

by BitLess246
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Reelwright

No user-submitted related servers found.

    Related Servers

    • WeCut

      13kailouis-stack
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to edit video locally through FFmpeg: probing media, validating and previewing JSON edit projects, rendering short-form clips with captions, reframing, transitions and ducked music. Also analyses existing videos and applies or saves reusable format templates, without cloud services or API keys.
      1
      Apache 2.0

    • cutroom

      0xpratzyy
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to edit talking-head videos locally by transcribing footage, applying validated edit operations like cutting fillers and silences, adding zooms, captions, looks and branding, and checking results with rendered previews. Agents can also read pinned editor feedback notes with annotated frames, resolve them, and export MP4, SRT or OTIO while the user watches changes live.
      52 npm
      1
      MIT

    • vidcut

      mao-data
      A
      license
      Not graded
      quality
      B
      maintenance
      AI-native timeline editor for short-form video. Your agent cuts, captions, adds motion graphics and renders against a real, editable timeline over MCP — not a render queue. Human-in-the-loop by design: it calls request_review and waits while you supervise in a browser. Local-first and AGPL; your footage never leaves your machine.
      2
      AGPL 3.0
    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

    B3/5.0

    Scored across 37 tools

    Disambiguation4/5

    Most tools map cleanly to one resource+action (clips, text, music, notes, transcripts), and the analysis tools (detect_scenes, detect_silence, audio_loudness, audio_waveform) are clearly separated. The only real blur is the preview trio — check_frames vs timeline_contact_sheet both render grids of the edited timeline, and inspect_media does the same for source assets — plus remove_silences overlaying detect_silence/delete_range. Descriptions do enough to steer an agent, but those pairs could be misselected.

    Naming Consistency4/5

    Strong verb_noun snake_case pattern: add_clip, trim_clip, split_clip, delete_clip, move_clip, add_text/update_text/remove_text, add_music/remove_music, add_note/list_notes/resolve_note. The deviations are few and readable — noun-phrase analysis tools (audio_loudness, audio_waveform, timeline_contact_sheet) and bare commands (undo, redo, history, export, transcribe). Nothing chaotic, just minor convention drift.

    Tool Count3/5

    37 tools is heavy for a single server, though the domain (ingest, analyze, edit, overlay, caption, render) genuinely demands breadth and almost every tool is doing distinct work. It still sits well past the comfortable 3-15 range and the preview/inspection cluster in particular feels padded. Borderline heavy rather than gratuitous.

    Completeness4/5

    Coverage is unusually deep: full clip lifecycle (add/trim/split/delete/move/volume/delete_range), overlays and music CRUD, transcripts, undo/redo/history, preview and final export with caption handling. Gaps are minor but real — no delete_project or asset/media removal, no read-side settings getter, and no transitions or fades between clips. Agents can work around these, but a few lifecycle ends are dead.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources